A recent commit on Emacs master branch changes the return value of
pp:
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=d3311499339fab0371cb7502a1e2481fbcd2c65d
The function does not document a stable return value, either.
This causes babel emacs-lisp source blocks to return "nil" for t
I submitted my assignment form this week, but I'm not sure how long it
takes for that to get processed. In the meantime, I'm attaching the latest
version of my patches for capture buffer tangling, updated with feedback.
If there are any other suggestions or concerns with the patches I can
address t
Ihor Radchenko writes:
> Morten Kjeldgaard writes:
>
>> The subject says it, it would be very nice if there was an export option
>> to export to text mode without wrapping paragraphs,so the resulting text
>> file can be read with visual-line-mode on.
>
> See org-export-preserve-breaks. Does it
Ihor Radchenko writes:
>>> I am exporting an Org file that contains a large verse block to
>>> LaTeX. This verse block contains footnotes, but they appear in the page
>>> where the LaTeX verse environment ends. I looked at the exported .tex
>>> file and I noticed that it was using "\footnotemark"
Rudolf Adamkovič writes:
> Actually, I found a problem: If I add a new Emacs Lisp code block to my
> literate Emacs configuration, Emacs launches with a blank screen,
> asking:
>
> Buffer ... modified; kill anyway? (yes, no, save and then kill, ?):
With clocks, it gets even weirder:
Org asks
Björn Bidar writes:
>>> * Preconditions
>>> - gnus-other-frame-object is a dead frame
>>
>> May you please describe when `gnus-other-frame-object' could become a
>> dead frame?
>
> I assume when the frame that is in the object was closed.
>
> E.g. for example to trigger this state again I closed
* lisp/org-clock.el (org-clock-kill-emacs-query): Reword the "Clock
out and save?" message to "Clock out before saving?" to convey the
important fact that no data will be lost when answered "no".
---
lisp/org-clock.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/org-clo
Rudolf Adamkovič writes:
> * lisp/org-clock.el (org-clock-kill-emacs-query): Reword the "Clock
> out and save?" message to "Clock out before saving?" to convey the
> important fact that no data will be lost when answered "no".
I forgot to prefix the commit title with the package name.
See the a
> On 2025-02-02 08:38, Uwe Brauer via General discussions about Org-mode.
> wrote:
> Yes :D
> but let's keep the discussion in the mailinglist in English so other
> people can participate, or benefit from it
Sure!
> In fact you don't need ~my/get-inactive-timestamp~ for your pursposes,
>
On 2025-02-02 21:02, Uwe Brauer via General discussions about Org-mode.
wrote:
A last question though.
Now if I want my headings look like
* <2025-02-02 08:58> Second entry
* <2025-02-02 08:53> First
* <2025-02-02 08:56> third
Is there any way to sort these heading with respect to the time
Hello,
The attached org file gives an example of output from an octave code block
that is unexpected and inconsistent. The problem is that disp("\n") does
not print a new line. The problem only occurs when the ":session" header
is used.
Paul
Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux
Hi all,
I hope this email finds you well. This is my first time contributing to
this mailing list attempting to contribute to org-mode, so hopefully I
do this correctly.
I recently noticed that `org-string-width` ran all buffer hooks like
`buffer-list-update-hook` for the ` *Org string width*` bu
Max Nikulin writes:
> Sorry if I confused everything. Does it mean that loading of mu4e will
> cause immediate loading of ol and so whole org? Is it acceptable to use
> `with-eval-after-load' in packages?
Thanks for bringing this up. AFAICT, requiring mu4e already loads all
of org. It probably
Zororg via "General discussions about Org-mode."
writes:
>> - common arguments are listed in a dedicated wiki page
>
>> https://orgmode.org/worg/org-tutorials/org-lookups.html
>
> This link seems unrelated. If I'm not wrong the expected link was
> https://orgmode.org/worg/topics/how-many-fi
Dear all,
Another OrgMeetup will be scheduled on the second Wednesday of February,
in 10 days.
*Note that we are back to using BBB server for the meetup (thanks to
Sacha Chua)*
Previous meetup notes:
https://list.orgmode.org/87y0ysb20i.fsf@localhost/T/#u
WORG page with earlier notes and meet
Rudolf Adamkovič writes:
> Rudolf Adamkovič writes:
>
>> * lisp/org-clock.el (org-clock-kill-emacs-query): Reword the "Clock
>> out and save?" message to "Clock out before saving?" to convey the
>> important fact that no data will be lost when answered "no".
>
> I forgot to prefix the commit tit
On 2025-02-02 08:38, Uwe Brauer via General discussions about Org-mode.
wrote:
Vale, entendido (supongo que eres español, porque usas la palabra movil,
¿correcto?)
Yes :D
but let's keep the discussion in the mailinglist in English so other
people can participate, or benefit from it
Thanks,
Hi Amy,
That sounds awesome! Unfortunately, I couldn't attend FOSDEM on
Saturday. Do you know if your talk has been recorded? It would be great
if we could watch it later.
Best regards,
Lennart.
On 30-01-2025 11:31, Amy Grinn wrote:
Hello all,
I hope you can join me in person or online
Ihor Radchenko writes:
>> I am using Org mode version 9.6.15 in GNU Emacs 29.4.
>
> Have you tried Org 9.7?
Canceled.
Most likely, this has been fixed already.
See https://list.orgmode.org/orgmode/87ikrdtf8u@gmail.com/
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Or
19 matches
Mail list logo
