> Thanks for taking a look! It indeed seems that caching will be the most
> work to properly implement. However, I'm quite happy to not care about
> numbers for now and make sure the other stuff works correctly first
> before tackling this.
Sure, this is a disproportionate amount of work for a min
On Sun, Apr 07 2024 10:48, Karthik Chikmagalur wrote:
> [… 14 lines elided …]
>
> There are two issues with numbering:
> - providing an Org-agnostic API point to attach a numbering table to, and
> - calculating the new numbering table in LaTeX (or other major-modes).
>
> For The first issue, we nee
> Abstracting away previews is certainly welcome.
> RMS explicitly asked Org mode team to work towards this goal:
> https://list.orgmode.org/e1kikxv-0007iy...@fencepost.gnu.org/
I agree with RMS about this, and this was on our minds when we wrote
org-latex-preview. The basic previewing process is
Hi Tony,
Just tried it out, it's very promising! Thanks for taking the initiative
on this.
> I've prodded the code a little bit and, mostly just following [1],
> managed to implement basic previews in a relatively straightforward
> fashion. Attached is a proof-of-concept—aptly named
> latex-late
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)
I tried to understand the code of org-timer-set-timer. It runs
(org-entry-get nil org-effort-prope
"Christopher M. Miles" writes:
> When I move point on the headline tags position. I evaluate
> `(org-element-at-point)` or `(org-element-context)`, both return element
> type is `(headline )`. I hope those two functions can return more
> explicit element type like "tags".
> I tried to find t
Tony Zorman writes:
> I'm interested in adjusting org-latex-preview to work in other major
> modes (most notably LaTeX-mode itself, so one can get rid of preview.el).
> On the advice of Karthik (Cc'd) I'll move the discussion from private
> mails to this list, so more people who might be interest
Max Nikulin writes:
> I think the following should be taken into account: behavior of popular
> calendar applications, specifications they implement, libraries that
> likely used to create such applications.
### what happens in google calendar if you repeat task monthly at 31st day of
month a
Morgan Smith writes:
> See two patches attached. One for org and one for worg. Tests still
> pass on my end.
Thanks!
>> In addition to changes in Org git, you also need to update
>> https://orgmode.org/worg/org-syntax.html#Timestamps and
>> https://orgmode.org/worg/dev/org-element-api.html(th
Ihor Radchenko writes:
> Confirmed.
>
>> Other failing commands are for example changes of todo state in agenda
>> buffer.
>>
>> The reason seems that org-agenda-get-restriction-and-command calls
>> delete-other-window; however, this is not something user observes and
>> expects as effect of thos
Ihor Radchenko writes:
> It has been a couple of months since the last activity in this thread.
> May I know if you are still interested to work on this feature?
No followup has been received within over half a year.
I am thus closing this ticket.
Canceled.
Feel free to re-open if there is any
When I move point on the headline tags position. I evaluate
`(org-element-at-point)` or `(org-element-context)`, both return element
type is `(headline )`. I hope those two functions can return more
explicit element type like "tags".
I tried to find this type API function in existing function
Hi,
I'm interested in adjusting org-latex-preview to work in other major
modes (most notably LaTeX-mode itself, so one can get rid of preview.el).
On the advice of Karthik (Cc'd) I'll move the discussion from private
mails to this list, so more people who might be interested can join in.
I've pro
13 matches
Mail list logo
