On Mon, Dec 26, 2022 at 06:47:37AM +, a...@bitrot.link wrote:
> Likewise, is the inability to close an org-mode outline section without
> starting a new section really a feature? [...] Or is
> the restriction really just a bug with seniority, and the difficulty of
> fixing it (or the
Hi fellow Orgers,
I've been using clock tables for some time now, and they are very
useful. However, it has just occurred to me that I'd really appreciate
another feature - a "task table". By this, I mean a table (generated
much like a clock table) with a summary of all tasks in a given
https://orgmode.org/worg/org-faq.html#closing-outline-sections answers
the question:
"Can I close an outline section without starting a new section?"
The answer given is:
"no. Org-mode adheres to the cascading logic of outlines, in which a
section is closed only by another section that
On Sun, 25 Dec 2022 06:23:53 -0500 Ihor Radchenko wrote ---
> As you see, "%S" have been used previously for non-string results.
> I cannot find explanation in git log.
>
> That said, I think that it will be more consistent to leave strings
> specifically as is. See the attached
Thanks a lot Ihor for looking at this. I followed the discussion in the
linked mailing list. I write a lot in Emacs and this gets rid of a long
standing annoyance. :) Cheers!
On Thu, Oct 27, 2022 at 11:08 PM Ihor Radchenko wrote:
> Ihor Radchenko writes:
>
> > I have forwarded this bug report
Also, it moves you to an outer level if you are at an end.
For my own use, because I want the command to treat the first item in a
list the same way as the others (when moving forward), I tweaked
org-forward-element from
(let* ((elem (org-element-at-point))
to:
(let* ((elem (progn
I have set up my org-mode so that I use variable pitch fonts for most of the
items and fixed pitch fonts for verbatim and src blocks.
This works as expected for languages babel knows by default, for example
emacs-lisp, python and c++.
However, I get variable pitch fonts for when I use an
* Ihor Radchenko [2022-12-25 15:07]:
> Jean Louis writes:
>
> >> > Apparently C-c C-e is capturing all events and not just keyboard
> >> > events!
> >
> > That is not first complaint, right? I would say it is obvious that
> > such interface is not user friendly.
>
> Yes and no. Some users do
"David O'Toole" writes:
> CSV export for the agenda is formatting January 1, 2023 as "2023-1-1" and
> not "2023-01-01".
> The raw output is here: https://pastebin.com/raw/EyN1JbhP
Could you please provide detailed steps how to obtain the erroneous CSV
output? See
alain.coch...@unistra.fr writes:
> Hello.
>
> I do
>
>emacs -Q -l ~/.emacs.git
> ...
Thanks for reporting!
Fixed on bugfix.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f13881006
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=718e19683
--
Ihor Radchenko
Jean Louis writes:
>> > Apparently C-c C-e is capturing all events and not just keyboard
>> > events!
>
> That is not first complaint, right? I would say it is obvious that
> such interface is not user friendly.
Yes and no. Some users do not like it. Some users prefer the existing
one.
On 18/12/2022 22:40, Stefan Monnier wrote:
Could Someone™ investigate why that code
doesn't do its job.
The code in question is in `package--reload-previously-loaded` and
my understanding is that it should cause `org-macs` to be reloaded
I do not see obvious flaws in
Hugo Cisneros writes:
> I use org-cite with a JSON bibliography and noticed a bug when an entry only
> has
> an "editors" field but no "authors" field. The function
> `org-cite-basic—get-author' correctly falls back to using the editors instead
> of
> the authors, but
On Sun, Dec 25, 2022 at 09:30:00AM +, Ihor Radchenko wrote:
> writes:
>
> >> Another idea is to avoid caching of parse result for small files.
> >
> > I haven't been following along very closely, but seeing the
> > involved complexities, I'd appreciate a knob to disable caching
> >
Matt writes:
> For :results list, the manual says, "Interpret the results as an Org list.
> If the result is a single value, create a list of one element". I don't find
> that clarifies what would be best.
>
> Thoughts?
In my patch, I followed the previous code branch:
(list (if (stringp
Tom Gillespie writes:
> From 4a78e1b5ea98dee569ff690037c661ab5c300194 Mon Sep 17 00:00:00 2001
> From: Tom Gillespie
> Date: Sat, 10 Dec 2022 12:11:17 -0800
> Subject: [PATCH 1/2] ob-core: add org-confirm-babel-evaluate-cell custom
> variable
Bastien, may you please take a look at this
Tom Gillespie writes:
> One more correction. The source of the issue is that the two values in the
> list need to be different, one for the message and one for the actual test.
> Best,
> Tom
>
> (list "emacs-lisp" cell
> '((:eval . yes)) nil (format "%S" cell)
>
Max Nikulin writes:
> I have tried the following in Emacs-27. For Emacs >= 29 add -L to Org <=
> 9.5.
>
> - "emacs -l org" to simulate a regular user session with some opened files.
> - Update to Org-9.6 from ELPA.
> - Close emacs and start it again "emacs -l org"
>
> Result:
> byte-code:
Max Nikulin writes:
> If you demonstrate that e.g., when working with encrypted files, their
> sensitive content leaks to the cache then it will raise the severity of
> the issue.
Nothing related to encrypted files is ever written by org-persist.
Some edge cases might exist for org-crypt, but
writes:
>> Another idea is to avoid caching of parse result for small files.
>
> I haven't been following along very closely, but seeing the
> involved complexities, I'd appreciate a knob to disable caching
> altogether.
org-element-cache-persistent
> My usage of Org hasn't triggered any
Max Nikulin writes:
> Ihor, I do not like that after your latest changes temporary directory
> became world readable.
This is the only sane way for emacs -Q, AFAIK. And the cache will now
only exist while Emacs is running (for -Q cmd arg). Removed
unconditionally upon exiting.
--
Ihor
Greg Minshall writes:
>> Do we need to care about cleaning up /tmp?
>
> my two cents is that maybe one should not care so much about cleaning up
> /tmp, but i think it's worthwhile trying not to clutter it up too much.
I improved things a tiny bit more.
Now, whatever is created by emacs -Q will
Marcin Borkowski writes:
>> org-forward-element
>> org-backward-element
>>
>> These two should be mentioned in the manual in section 2.3 "Motion"
>
> How are they different from `org-forward-heading-same-level` and
> `org-backward-heading-same-level'? (Not irony etc., I'm genuinely
> curious.)
On 2022-12-24, at 03:43, Peter Mao wrote:
> Dear maintainers,
>
> The following commands are missing from the manual!
>
> org-forward-element
> org-backward-element
>
> These two should be mentioned in the manual in section 2.3 "Motion"
How are they different from
24 matches
Mail list logo
