Re: [BUG] SPACE jumps to tag in header line after hidden emphasis marker [9.7-pre (release_9.6.7-562-g5b6268 @ /home/jschmidt/work/org-mode/lisp/)]

2023-07-19 Thread Farblos
On 2023-07-18 10:13, Ihor Radchenko wrote: Confirmed. Thanks for caring about this so quickly ... https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64696 ... and for the discussion with Eli & co. Which I did not try to follow TBH. Fixed, on main. https://git.savannah.gnu.org/cgit/emacs/o

Re: Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data

2023-06-11 Thread Farblos
On 2023-06-11 12:21, Ihor Radchenko wrote: This is a bug. Fixed now, on main. Thanks!

Re: Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data

2023-06-10 Thread Farblos
On 2023-06-10 22:47, Farblos wrote: Hang on, that test case is not really clean yet ... -Q disabled my load-path additions, of course ... will give it another try ... No, the test case is good and exactly as described in the mail before the previous one, even with "emacs -Q". Thanks

Re: Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data

2023-06-10 Thread Farblos
On 2023-06-10 22:39, Jens Schmidt wrote: OK, so I cobbled up Org main with branch emacs-29. Hang on, that test case is not really clean yet ... -Q disabled my load-path additions, of course ... will give it another try ... Sorry.

Re: Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data

2023-06-08 Thread Farblos
Thanks for the clarification. On 2023-06-08 13:17, Ihor Radchenko wrote: Note that we had some bugs in this area in older Org versions. I happen to have master from git://git.savannah.gnu.org/emacs.git checked out here. How recent is that w.r.t. "bleeding edge Org" from git://git.savannah.g

Where does headline data end for the purpose of `org-adapt-indentation´ == ´headline-data

2023-06-08 Thread Farblos
I like the idea of org-adapt-indentation being ´headline-data: When this variable is set to ‘headline-data’, Org only adapts the indentation of the data lines right below the headline, such as planning/clock lines and property/logbook drawers. However, I find the resulting indentation beha

Re: [BUG] Filling in source blocks fills by region, not paragraph [9.5.5 (release_9.5.5/master)]

2023-04-29 Thread Farblos
Forget about that one, it is already fixed in master. During my first test I used the wrong load path and thus used the distribution-provided org-mode version.

[BUG] Filling in source blocks fills by region, not paragraph [9.5.5 (release_9.5.5/master)]

2023-04-29 Thread Farblos
Cloned https://git.savannah.gnu.org/git/emacs/org-mode.git, changed to directory "org-mode", made "autoloads", started Emacs as "emacs -Q -L $PWD". In an otherwise empty org-mode buffer, create a block #+begin_src shell # configure shell options and variables. bash-completion # requires shell o

Re: [ENHANCEMENT] Make `org-babel-do-in-edit-buffer' environmentdetectable

2023-03-10 Thread Farblos
> We have org-edit-prep:lang functions that do initial setup in individual > languages. However, they will be applied both when you call > `org-babel-do-in-edit-buffer' and in C-c '. I have no problem with these being called in both cases. However, as functions they would be "extensible" only by

[BUG] `org-entry-put' creates a new property drawer if case folding is turned off [9.5.2 (9.5.2 @ /usr/share/emacs/site-lisp/elpa/org-9.5.2/)]

2023-03-07 Thread Farblos
To reproduce, start on a Bourne shell command line with cat << EOF > foo.org * heading heading heading :properties: :foo: bar :end: EOF Then start emacs -Q foo.org In Emacs continue: M-x set-variable RET case-fold-search RET nil RET C-c C-x p foo RET bar RET For me Org then creates a new pro

[ENHANCEMENT] Make `org-babel-do-in-edit-buffer' environment detectable

2023-03-07 Thread Farblos
Concrete use case: I got fed up by sh-mode notifying me about "Indentation setup for shell type bla" when editing shell source blocks in an Org buffer. (To reproduce, start "emacs -Q", open an empty org file, create a shell source block with contents " echo foo", and press TAB on that line.)