Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

Eli Zaretskii writes: >> >> In addition, `org-kill-line' acts specially in certain scenarios: >> >> >> >> For >> >> * Heading text :tag1:tag2: >> >> >> >> `org-kill-line' will keep and re-align ":tag1:tag2:": >> >> >> >> * Heading :tag1:tag2: >> >> >> >> It would be nice if we could ex

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

Sebastian Miele writes: >> I think there is misunderstanding. `combine-after-change-calls' will not >> affect the two-step modification of the kill ring, if we put it around >> `kill-whole-line'. Or do I miss something? > > I tried to wrap the problematic portion of `kill-whole-line' into > `comb

Re: [Bug] Some parentheses are not visible in the html export but are present

Niall Dooley writes: > Some parentheses are not visible in the html export but are present. This > was not always the case with the provided example. > > --- Begin Example --- > ... > The parentheses under the Back subheading are displayed in the export. > However, the parentheses within the src

Re: [BUG] wrong-type-argument listp 4240 [9.7-pre (release_9.6.8-749-g4fe52f @ .emacs.d/org-mode-git/lisp/)]

Paul Stansell writes: > I don't know what caused the following message when I opened an org file, > but I'm reporting it as requested by the message: > > Warning (org-element-cache): org-element--cache: Org parser error in > tmp_train_notes.org::1. Resetting. > The error was: (wrong-type-argumen

Re: Possible File Saving Bug with [/]?

Samuel Wales writes: > lock file? in 27 (info "(emacs) Interlocking") strangely does not > mention .# but it could be the concept in question. #... is a backup file. There is nothing wrong or surprising about it. However, the bug report is not clear enough for me to try reproducing things on m

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

> From: Ihor Radchenko > Cc: i...@whxvd.name, 65...@debbugs.gnu.org, emacs-orgmode@gnu.org > Date: Thu, 07 Sep 2023 10:00:49 + > > Eli Zaretskii writes: > > > Then perhaps just a special value for buffer-invisibility-spec, or > > some other simple variation of a property Org already uses? >

Re: Fallback fonts in LaTeX export for non latin scripts

Juan Manuel Macías writes: >> Do I understand correctly that onchar=id will not break anything if text >> is correctly marked with \selectlanguage{}? > > To load language features (hyphen rules, captions, etc.) there is no > problem. But to load a font associated with a language, the font of the

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

> From: Eli Zaretskii > Date: Thu, 2023-09-07 13:19 +0300 > >> From: Ihor Radchenko >> Cc: i...@whxvd.name, 65...@debbugs.gnu.org, emacs-orgmode@gnu.org >> Date: Thu, 07 Sep 2023 10:00:49 + >> >> Eli Zaretskii writes: >> >> > Then perhaps just a special value for buffer-invisibility-spec,

Re: ox-latex language handling in Org-9.5 vs 9.6

On 07/09/2023 05:20, Juan Manuel Macías wrote: Maybe it should be corrected like this: ("de-de" :babel "ngerman" :polyglossia "german" :polyglossia-variant "german" :lang-name "German") ("de" :babel-ini-only "german" :polyglossia "german" :polyglossia-variant "german" :lang-name "German")

Re: Possible File Saving Bug with [/]?

Hi! Sorry for the delay in replies. I was super busy yesterday, last night, and this morning. Ok! Let’s get to it: 1) I’m not going to reproduce the bug because it’s super annoying for me to try to get rid of because I have to kill extra buffers to do it, restart emacs, fix the git repo etc…and

Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3

Max Nikulin writes: >> Max Nikulin writes: >>> I am unsure if any "PREFIX:" should be recognized as a link type, but >>> there is another possibility on this way: allow users to mark some >>> prefixes as search links, not link types. >> >> May you elaborate? > > I am considering another behavior

Re: Possible File Saving Bug with [/]?

Summer Emacs writes: > 3) In one of the headers, it looked something like this: > * C-c C-c on [/] to update done items in todo list. > > That [/] just like that was creating a backup file on every save named > .#emacshelp.org# —> summer@summer.local.23434:882343 (those are made up > numbers bu

Re: [BUG] Consider supporting C-x 4 and C-x 5 and C-x t in org-open-at-point [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

Vladimir Nikishkin writes: > Emacs has a long established tradition of adjusting presentation mode > for a command using prefix parameters. True. > ... One can run C-x 4 C-f to visit a > file in a new window. (C-x 5, and C-x t for the new frame and tab, > respectively). ... but C-x 4 is not a

Re: Possible File Saving Bug with [/]?

> On Sep 7, 2023, at 12:49, Ihor Radchenko wrote: > > Summer Emacs writes: > >> 3) In one of the headers, it looked something like this: >> * C-c C-c on [/] to update done items in todo list. >> >> That [/] just like that was creating a backup file on every save named >> .#emacshelp.org# —

Re: [BUG] Consider supporting C-x 4 and C-x 5 and C-x t in org-open-at-point [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

Ihor Radchenko writes: > Vladimir Nikishkin writes: > >> Emacs has a long established tradition of adjusting presentation mode >> for a command using prefix parameters. > > True. > >> ... One can run C-x 4 C-f to visit a >> file in a new window. (C-x 5, and C-x t for the new frame and tab, >>

Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3

On 07/09/2023 17:42, Ihor Radchenko wrote: Max Nikulin writes: I am considering another behavior. If any PREFIX: is recognized then the link exported literally as PREFIX:PATH unless the PREFIX is registered as (org-link-register-search-link-prefix "sec") So if the document does not conta

Re: Possible File Saving Bug with [/]?

Summer Emacs writes: >> Without more information, I cannot provide more assistance >> unfortunately. I also do not see how we can help on Org side as the >> problem _appears_ to be with your personal config. >> > > Again: My config works with all of my other files. Every single one. Org > files

Re: [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3

Max Nikulin writes: >> >> I feel that it will be too complex. >> We might simply throw a warning when we get unregistered [[type:path]] >> link, so that the user can notice if there is any problem. > > I do not think it noticeably increases complexity in comparison to the > current state of aff

Re: [MAINTENANCE] On how much we can expose internals into defcustom

Leo Butler writes: >> ... >> In order to make such a switch, we will have to force all the users >> change their customization - something we do not want to annoy users >> with. > > I understand your general argument, but I doubt it is relevant to this > particular case. > > In this specific case

Re: Tips on reproducing and bisecting bugs

Rens Oliemans writes: > Thanks for creating and maintaining Org mode, it's great. I tried helping out > recently by > confirming and bisecting a reported bug > (https://list.orgmode.org/camjkazz6srdoxv6rhmdm97enhysntodtctcznn1zbquk3gh...@mail.gmail.com/), > but am not sure if what I did was actu

Re: ox-latex language handling in Org-9.5 vs 9.6

Juan Manuel Macías writes: > Max Nikulin writes: > >> I consider the following as an issue rather close to the discussion in >> the thread >> Juan Manuel Macías. Fallback fonts in LaTeX export for non latin >> scripts. Wed, 30 Aug 2023 08:25:53 +. >> https://list.orgmode.org/878r9t7x7y@

Re: Missing changes

Po Lu writes: > OK, thanks. As an aside, which versions of Emacs does Org presently > support? Emacs 29, 28, and 27. See https://orgmode.org/worg/org-maintenance.html#emacs-compatibility -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at .

Re: Fallback fonts in LaTeX export for non latin scripts

Ihor Radchenko writes: > May we explicitly set the needed font around language environments? > > Something like > > \setfontforrussian > \selectlanguage{russian} > > > \setfontforbulgarian > \selectlanguage{bulgarian} > There's no need. With \babelfont you can associate a font with a la

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

Eli Zaretskii writes: >> We may have a misunderstanding here. >> In "* Heading text :tag1:tag2:", everything is visible yet Org needs to >> protect ":tag1:tag2: from being killed by `kill-line', but not from >> `kill-whole-line'. Moreover, the behaviour also depends on the point >> position - if

Re: bug#65734: [BUG] kill-whole-line on folded subtrees [9.6.8 (release_9.6.8-3-g21171d @ /home/w/usr/emacs/0/29/0/lisp/org/)]

Sebastian Miele writes: >>> Then, what should we do to move things forward? I guess the first step >>> will be writing these missing tests. >> >> Yes, that'd be most welcome. > > I will write the tests. And I will probably come up with an updated > version of the original patch. There is at lea

Help me contribute to org

To whom it may concern, I would like to contribute to org-mode but I have no experience with git. I would like to start with something small - adding translations for my language. Could somebody please guide? Kind regards signature.asc Description: PGP signature

Re: ox-latex language handling in Org-9.5 vs 9.6

Ihor Radchenko writes: >> In both lists the language code for German is simply "de". Of course, >> I'm no expert on the subject, so if I'm wrong in this case, I should >> revert the change. I understand that de-de is German of Germany (="de"?); on >> org-latex-language-alist exists de-at (Austrian

Re: [PATCH] Add tests for ob-haskell (GHCi)

Hi Ihor, Sorry for the delay, thanks again for the ping. Ihor Radchenko writes: > Bruno Barbier writes: > + (when (bufferp "*haskell*") (error "Conflicting buffer '*haskell*', rename it or kill it.")) + (with-current-buffer session (rename-buffer "*

Re: ox-latex language handling in Org-9.5 vs 9.6

On 07/09/2023 21:19, Juan Manuel Macías wrote: I think I can introduce some fixes to org-latex-language-alist to restore the removed language codes I have no idea why in 393f2f5ae 2012-06-14 12:57:35 +0200 Nicolas Goaziou: org-e-latex: Set Babel language according to LANGUAGE keyword new "n

Re: [BUG] Consider supporting C-x 4 and C-x 5 and C-x t in org-open-at-point [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

On 07/09/2023 17:54, Ihor Radchenko wrote: I think that it will be acceptable to add new bindings like C-x 4 C-c C-o and C-x 5 C-c C-o that will open a link in other window or frame, if possible. Patches welcome! Is it possible to make such bindings local to Org? E.g. `ffap-bindings' (info "(em

Re: [Bug] Some parentheses are not visible in the html export but are present

On Thu, 7 Sept 2023 at 12:07, Ihor Radchenko wrote: > I am unable to reproduce. May you please provide a more detailed recipe > starting from emacs -Q? See https://orgmode.org/manual/Feedback.html#Feedback With your suggestion it no longer occurs. Off to bisect my init.el. Sorry for the noise.