Ihor Radchenko writes:
> Max Nikulin writes:
>
>> On 09/04/2024 15:52, Ihor Radchenko wrote:
>>> Aside: It looks like your public branch is not up-to-date as the time
>>>of writing this email - I do not see commits changing the syntax to
>>>@foo{...} and @@{...} yet,
>>
>> Do you have in
actually you migt be betst ignoring the notes as they were written many
years before even the tses in it. but the code wfm.
On Wednesday, April 10, 2024, Samuel Wales wrote:
> to me, the concepts of the log mode feature and the showing inactive tses
> feature are so close that they are worth
to me, the concepts of the log mode feature and the showing inactive tses
feature are so close that they are worth merging into the same
functionality, parameterized if needed [not needed for me].
in my own case, i basically want all [log mode and inactive tses] off or
all on. years ago, i
Apologies for the delay. I had lots of social events surrounding the
solar eclipse. The eclipse was really cool, I do recommend.
See two patches attached again. All tests pass on my computer.
I decided to add an extra `let' statement to my changes to
`org-element-timestamp-parser'. I think
Thank you Philip for the explanation and preparing the code snippet.
So what are the next steps?
Can you merge your patch?
--
Slawomir Grochowski
I'd like to suggest adding a new prefix arg i.e.
`C-u C-u org-clone-subtree-with-item-shift' to reverse
the order of newly created / cloned siblings. Would
that be of interest for other orgmode users?
Diff file is attached.
--
Christian Barthel
diff -u --label \#\ --label \#\
"Fraga, Eric" writes:
> I tend to name every src block
> anyway as it makes navigation easier (using
> org-babel-goto-named-src-block).
I didn't know this function exist. Thank you very much. :)
Protesilaos Stavrou writes:
> Though I should have clarified my intent earlier: the idea is to use the
> label as a fixed reference to the footnote, so that the link does not
> change between exports. This is the same principle as what we do with
> links to headings that have a CUSTOM_ID.
>
> As
Russell Adams writes:
> I pull up a file in 'emacs -Q'.
>
> M-x org-agenda 1 a (restricted to current file, create agenda view).
> Now viewing the weekly agenda in buffer *Org Agenda*.
> Press "L" to enable logbook.
> Press "[" to enable inactive timestamps.
>
> I now see the full week with
Daniel Clemente writes:
> Hi,
> after updating org-mode and emacs to latest commits, I have seen that
> some links to IDs in different files are exported like this:
> some link: link
>
> Shouldn't it be?: otherfile.html#c5m2je81pue0
It should be otherfile.html#ID-c5m2je81pue0
But what you
On Mon, Apr 08, 2024 at 07:31:10PM +, Ihor Radchenko wrote:
> Russell Adams writes:
>
> > I have noticed that when I pull up an agenda view, if I enable/disable
> > items (ie: enable logbook, enable inactive timestamps), that if I
> > change to a new time period (ie: forward/backward
William Denton writes:
>> Do you still see it on your side?
>
> Thanks for following up. No, I don't see it any more ... an ESS upgrade or
> something fixed the problem.
Thanks for checking!
Canceled.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at
Björn Bidar writes:
> The bug also seems to affect `org-attach`.
Fixed, on main. Alongside with other similar places.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=78e9dd0c4
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at
Bhavin Gandhi writes:
> When running org-timer-set-timer (bound to `;') in an Org agenda buffer,
> I get following warning:
>
> ⛔ Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org
> buffer # (org-agenda-mode)
Fixed, on main.
Dear all,
Another OrgMeetup will be scheduled on the last Wednesday of February,
in two weeks. (Sorry, I cannot make it second Wednesday this time, and
even third.)
Previous meetup notes:
https://list.orgmode.org/87ttk9hbhv.fsf@localhost/T/#u
URL: https://bbb.emacsverse.org/b/iho-h7r-qg8-led
Sławomir Grochowski writes:
> Philip Kaludercic writes:
>
>> We could add a `help-quick-use-map' variable and bind it to `global-map'
>> by default. You can then re-bind it in your command.
>
> I'm sorry, but I don't quite understand it.
Just this here:
diff --git a/lisp/help.el
[ This time, the meeting notes are incomplete. I only took partial
notes and then came back to them after a long time, when I had only
selective long-term memory to work with. ]
- Gerard showcased interactive interface to select different export
styles for code blocks when exporting to
Chang Xiaoduan writes:
> I am trying to customizing `org-emphasis-alist` so that ` can replace ~ as
> the code marker. I use the following code in my configuration file:
>
> ``` emacs-lisp
> (setq org-emphasis-alist
> '(("*" bold)
> ("/" italic)
> ("_" underline)
>
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Thank you Ihor for looking into this!
> From: Ihor Radchenko
> Date: Fri, 5 Apr 2024 14:33:49 +
> [... 13 lines elided]
>> I looked into the ox.el and noticed that the export data does include
>> the labels. But 'org-html-footnote-reference' does not have a call to
>> get the label: it
On Tuesday, 9 Apr 2024 at 18:58, Sébastien Gendre wrote:
> If I name the source block, it work.
Excellent.
> Is it because:
>
> * When a source block is named, it's result is also named
>
> * When a result is named, Org-mode can locate it and replace its value
>
> * But when a result is not
21 matches
Mail list logo
