> The attached patch adds support for $…$ latex fragments followed by a
> dash, such as $n$-th.
Unfortunately this falls into the realm of changes to syntax. The current
behavior is not a bug and is working as specified because hyphen minus
(U+002D) does not count as punctuation for the purposes
FWIW, day *does* update in lines like, "SCHEDULED: <2022-01-25 Tue .+1d>".
Interestingly the timestamp is angle-bracketed rather than
square-bracketed. Hmm
On Thu, Jan 20, 2022 at 11:13 PM Eli Zaretskii wrote:
> > From: "Bruce E. Robertson"
> > Date: Tue, 18 Jan 2022 10:36:22 -0800
> >
> >
>
On a personal note, I would be very happy to see this patch merged. It has
been annoying me for years, see for instance this thread:
https://emacs.stackexchange.com/questions/37207/org-latex-fragment-succeeded-by-a-dash-is-not-showing
Goran
Hello,
I make use of
(setq org-log-done 'note
org-log-reschedule 'note
org-log-delschedule 'note
org-log-redeadline 'note
org-log-deldeadline 'note
org-log-refile 'note)
But would like to also add a note when for org-log-schedule. I will add this to
Hi Juan,
Thanks for your answeer.
Indeed, the generated tex files are different whether you use the png or
svg extension.
It seems that for svg, a distinct build system is used from the usual
one for other image types (png, jpg).
This build system seems based on tex4ht, given the latex file
Thank you so much Juan, I could adapt your filter to my needs, and this works
like a charm !
V.
De : Juan Manuel Macías
Envoyé : mardi 25 janvier 2022 18:30
À : Vincent Belaïche
Cc : orgmode
Objet : Re: [RFC] Creole-style / Support for
Just replying to myself : the dynamic latin9/utf8 switch does not really easily
work in a LaTeX document (I am sure some people made it work, but I did not
manage to make it).
Adding the ZWSP support is easy, just insert
\DeclareUnicodeCharacter{200B}{}
in the document preamble, but this does
Hello,
Vincent Belaïche writes:
> Actually the source was in UTF-8,
Then use a zero-width space, and remove it from the output with
a filter.
Regards,
--
Nicolas Goaziou
Ugh. Thanks for that. Three contributing factors: a) doing a git pull/make
and seeing output as usual without really paying attention, b) scanning for
commit date, seeing January which seemed AboutRight but completely missing
the "oh right, it's 2022 now," and c) the root cause being it'd been so
Hello,
Actually the source was in UTF-8, but it was using only characters that exist
in latin-9, and it is exported to LaTeX for inclusion in a LaTeX document that
is in latin-9.
So I used an Emacs lisp snippet to make the export, and in this snippet after
calling something like
Hi Vincent,
Vincent Belaïche writes:
> My conlcusion is that for what I am after, an evolution of org-mode
> would be preferable, maybe I contribute something someday, so that
> writing one of the following would make it:
>
>~--my-option=~\relax{}/option value/
>
Ihor Radchenko writes:
> pareto optimal writes:
>
>> Using =emacs -Q= to tangle org files with more than over 100 noweb-refs gets
>> slow fast.
>>
>> Given this org code for N=2:
>> Using Gcc Emacs 28.0.91 (which I typicall use) I get these results:
>>
>> | N blocks | runtime | # of GCs |
>>
On Tue, Jan 25, 2022 at 4:39 AM Ihor Radchenko wrote:
> Thanks for the report!
>
> Can you try the following:
> 1. (setq org-element--cache-self-verify 'backtrace) in your init.el
>before loading org
> 2. Do whatever it takes to get question marks as category in agenda
> 3. Go to the
On 24/01/2022 19:32, Vincent Belaïche wrote:
Thank-you both for the reply, I should have mentioned that I am aware of
this trick but it works only for document encodings which have the
zero-width space, like UTF-8, I was after a fix for documents in
ISO-8859-15, aka latin-9.
I have a hope
Sébastien Miquel writes:
> pareto optimal writes:
>> Using =emacs -Q= to tangle org files with more than over 100
>> noweb-refs gets slow fast.
> I can reproduce the slow down with my config. The culprit is
> ~org-element--cache-verify-element~. Significantly decreasing
>
pareto optimal writes:
> Using =emacs -Q= to tangle org files with more than over 100 noweb-refs gets
> slow fast.
>
> Given this org code for N=2:
> Using Gcc Emacs 28.0.91 (which I typicall use) I get these results:
>
> | N blocks | runtime | # of GCs |
> |--+-+--|
> |
Hi,
pareto optimal writes:
Using =emacs -Q= to tangle org files with more than over 100
noweb-refs gets slow fast.
I can reproduce the slow down with my config. The culprit is
~org-element--cache-verify-element~. Significantly decreasing
=org-element--cache-self-verify-frequency= yields a 5x
Eugene Rakhmatulin writes:
> When any of the agenda files get updated outside of this instance of
> Emacs (e.g. another editor or in my case Emacs on another machine via a
> synced iCloud Drive folder), questionmarks are displayed instead of a
> file name. That does not always happen, but when
Using =emacs -Q= to tangle org files with more than over 100 noweb-refs gets
slow fast.
Given this org code for N=2:
#+begin_src org :tangle 2.org
,#+begin_src elisp :noweb yes :tangle 2.el
<>
,#+end_src
,#+begin_src elisp :noweb-ref some-reference :tangle no
;; comment
,#+end_src
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.
Hello,
Vincent Belaïche writes:
> Thank-you both for the reply, I should have mentioned that I am aware of
> this trick but it works only for document encodings which have the
> zero-width space, like UTF-8, I was after a fix for documents in
> ISO-8859-15, aka latin-9.
You mean the source
Hi,
Eric S Fraga writes:
But is not necessary (and further complicates the issue of support $...$
in org as recently discussed on this list) as you can simply type
\(n\)-th?
What complication are you referring to, precisely ?
The patch is fairly trivial, and a similar extension was already
Ihor Radchenko writes:
> Tim Cross writes:
>
>> Ihor Radchenko writes:
>>
>>> Also, it appears to me that we may keep losing terminal-incompatible
>>> keys in future unless we provide some mechanisms to check terminal
>>> compatibility automatically. Any ideas?
>>>
>>
>> No ideas on this.
org-revert-all-org-buffers is useful when synchronizing org data between
different systems. In that case, one has to also synchronize
clocking data. It would make sense to also run org-clock-load after
org-revert-all-org-buffers.
I didn't find an appropriate hook, is there a better way than
On Monday, 24 Jan 2022 at 16:42, Sébastien Miquel wrote:
> The attached patch adds support for $…$ latex fragments followed by a
> dash, such as $n$-th.
But is not necessary (and further complicates the issue of support $...$
in org as recently discussed on this list) as you can simply type
25 matches
Mail list logo
