TOC and latex memoir class
In order to place the table of contents without a section name "Contents" the memoir class uses \tableofcontents* rather than \tableofcontents. However, `org-latex-toc-command` is documented as: "LaTeX command to set the table of contents, list of figures, etc. This command only applies to the table of contents generated with the toc:nil option, not to those generated with #+TOC keyword." Which is confusing in two ways, first that toc:nil doesn't generate a table of contents, and that it doesn't seem to provide any way of getting the string to be used? As a workaround, I could use the latex command directly, but that means not having it available in, for example, an html export. Is there a workaround I'm missing?
buffer displays incorrectly after capture
I think there is a bug in updating an org buffer window after capture
appends an entry. When the previously final entry, terminated with a
newline, is folded, the newly captured entry that is appended does not
show correctly in the buffer. Here is an example capture template:
("a" "Actions" entry
(file "~/Documents/org/capture.org")
"* TODO %^{action} :action:" :immediate-finish t)
There is a single existing entry in capture.org:
* TODO foo :action:
some text[newline]
I fold the entry so that it appears in the buffer like this:
* TODO foo :action:...
Then from any buffer I type 'C-c c' and choose 'a' from the capture
template dispatcher. I type 'bar'. I would expect a new
headline to be visible at the end of capture.org. Instead, nothing
changes in the buffer. When I expand foo, it looks like this
* TODO foo :action:
some text...
No amount of tabbing causes the bar entry to display. The ellipsis at
the end of 'some text...' only gets expanded when I to cycle
global visibility, resulting in a correct display:
* TODO foo :action:
some text
* TODO bar :action:
Another manifestation of the problem shows up when using
auto-revert-mode. Starting with the single headline in a folded state
as above, when I execute the following command in a shell,
echo "* TODO bar :action:" >>capture.org
then the capture.org buffer looks like this:
* TODO foo :action:...* TODO bar :action:
TAB unfolding the first headline shows up like this:
* TODO foo :action:
some text...* TODO bar :action:
GNU Emacs 27.2 (build 1, aarch64-apple-darwin21.3.0, Carbon Version
165 AppKit 2113.3) of 2022-02-24
Org mode version 9.5.2 (release_9.5.2-423-g6d73cd)
problem with diary sexps
Hello all, I updated org today and now get Bad sexp at line 461 in /home/ucecesf/s/notes/diary.org: (let ((entry ) (date '(4 19 2022))) (diary-float t 2 3)) for a line that looks like <%%(diary-float t 2 3)> This has been in my diary for a very long time with no error. I wonder if this has anything to do with the changes to the use of advice? Nothing else in the recent changes in the git log seem to be relevant. Just a quick heads up as I don't have time to debug at the moment. It's not mission critical... Have a good weekend all. -- : Eric S Fraga, with org release_9.5.2-423-g6d73cd in Emacs 29.0.50
Re: Drop defadvice from Org
> i was ok with the scold for a long time about (` thing but my reactin > time slowed significantly and that was trivial-er. The (` transition was not handled ideally, to be honest: we declared them obsolete very early but only started emitting warnings much later, so the transition period have seemed short for those who only learned about it when the warning appeared. > 2040 is when i will begin figuring out or finding some long lost > convert thing, and then decide to do something about my carefully > self-cargo-culted advice. fortunately, debian on the trailing edge > will give me a bit more. Also, note that ever since `nadvice.el` appeared, `advice.el` was "reimplemented" as a layer on top of `nadvice.el`, so when it finally gets removed from Emacs, I'd expect that `advice.el` could be added to GNU ELPA for those who want to keep using it (typically because of some old and unmaintained package). [ The same might happen with `cl.el`. ] Stefan
Re: Drop defadvice from Org
On 3/31/22, Stefan Monnier wrote: > I definitely hope it will be gone before 2040, but it hasn't even been > declared officially obsolete yet (not even in `master`), so I think you > should be good at least until 2030. thanks. i was ok with the scold for a long time about (` thing but my reactin time slowed significantly and that was trivial-er. 2040 is when i will begin figuring out or finding some long lost convert thing, and then decide to do something about my carefully self-cargo-culted advice. fortunately, debian on the trailing edge will give me a bit more. still trying to get my scripts to understand the new branch names.
yanking into body text ends up after the entry
imagine this * to yank a b c * x ^sadfsadf ^^*** y if i kill the to yank entry, then paste at ^,it ends up at ^^ instead. this is logical in that to yank would swallow the body text, but i am wondering when this behavior started. when i kill to yank as a shortcut for moving its body text, my intention is to kill the header afterward. and so the behavior, is surprising. idk a command for "kill header and copy body". if that makes any sense.
