Re: [BUG] org-insert-heading changed behavior with Emacs 29.2 [9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.2/lisp/org/)]

2024-05-10 Thread gusbrs
Hi Ihor, On Fri, 10 May 2024 at 06:17, Ihor Radchenko wrote: > > I studied the code closer, and it looks like some parts of Org mode > already use `org-blank-before-new-entry' when deciding the blank lines > after newly inserted list items. So, instead of introducing a new > customization, I wen

Re: [BUG] org-insert-heading changed behavior with Emacs 29.2 [9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.2/lisp/org/)]

2024-02-03 Thread gusbrs
Hi, On Sat, 3 Feb 2024 at 10:27, gusbrs wrote: > On Sat, 3 Feb 2024 at 09:32, Ihor Radchenko wrote: > > Would it make sense to add a new `org-blank-after-new-entry' > > customization that will provide explicit user control over what Org does > > when inserting a new

Re: [BUG] org-insert-heading changed behavior with Emacs 29.2 [9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.2/lisp/org/)]

2024-02-03 Thread gusbrs
ective of C-RET alone, I'd be inclined to restate my suggestion of treating the issue that motivated that commit as a "visibility / folding" problem. However, including M-RET into the mix, I think you have a good point, and something like `org-blank-after-new-entry' would possibly help improve blank line consistency in general. Best regards, gusbrs

[BUG] org-insert-heading changed behavior with Emacs 29.2 [9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.2/lisp/org/)]

2024-02-01 Thread gusbrs
lded be treated as one of visibility / folding, not one of buffer contents. Best regards, gusbrs. Emacs : GNU Emacs 29.2 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, cairo version 1.16.0) of 2024-01-18 Package: Org mode version 9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.

Re: Force creation of org id in template

2020-10-26 Thread gusbrs . 2016
Hi Michael, On Mon, 26 Oct 2020 at 19:26, Michael Heerdegen wrote: > is it possible to tweak `org-capture-templates' entries so that the > creation of an org id for an org entry created with `org-capture' is > forced? Untested, but how about adding something like the following to your template