On 8 May 2023, Thomas S. Dye wrote:
Would it be useful for me to search for calls to the folding functions from
outline.el in the source code of the Org packages that Spacemacs and I load?
This problems happens to me regularly, and I don't use Spacemacs. Wherever it
is, I don't think it's
Ihor Radchenko writes:
> Nathaniel Nicandro writes:
>
>>> Ideally, fontifying ANSI sequences should be fully controlled by users:
>>> 1. We may not want to touch src blocks by default, when
>>>`org-src-fontify-natively' is set to t. Only, maybe, provide an
>>>option. Or you may better
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>>> You can. Or you can leave things unchanged.
>>
>> Well if I don't change I see the time stamps like this
>> <<09.05.2023 >
>> instead of
>>
>> <09.05.2023>
>>
>> When I use org-toggle-time-stamp-overlays
>> to toggle the overlays
Uwe Brauer writes:
>> You can. Or you can leave things unchanged.
>
> Well if I don't change I see the time stamps like this
> <<09.05.2023 >
> instead of
>
> <09.05.2023>
>
> When I use org-toggle-time-stamp-overlays
> to toggle the overlays on
I am unable to reproduce.
I did
1. /tmp/bug.el
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> But I have files with the setting
>>
>> #+begin_src emacs-lisp :results silent :exports none
>> (custom-set-variables
>> '(org-display-custom-times t)
>> '(org-time-stamp-custom-formats '("<%d.%m.%Y>" . "<%d.%m.%Y %I:%M %p>")))
>>
Ihor Radchenko writes:
> Yes. See `org-babel-common-header-args-w-values'. In particular, take a
> look at (results ...).
Thanks, it took me some time to get my head around how to use this.
> I now ported a bit of documentation from my refactor branch.
> See
Uwe Brauer writes:
> But I have files with the setting
>
> #+begin_src emacs-lisp :results silent :exports none
> (custom-set-variables
> '(org-display-custom-times t)
> '(org-time-stamp-custom-formats '("<%d.%m.%Y>" . "<%d.%m.%Y %I:%M %p>")))
> #+end_src
>
>
> Should I change that to
>
Hi
I just read in the news that
the Leading =<= and trailing =>= in the default values of
~org-time-stamp-formats~ and ~org-time-stamp-custom-formats~ are
stripped.
No changes on the user side are needed if
~org-time-stamp-custom-formats~ was customized.
But I have files with the setting
Max Nikulin writes:
> On 09/05/2023 18:34, Ihor Radchenko wrote:
>> I can easily see Lualatex-specific preamble simply failing to work on
>> Latex. Or things being rendered wrongly.
>
> iftex.sty has \ifpdftex and \iftutex (XeTeX, LuaTeX, LuaHBTeX) commands,
> so it is possible to create
Sébastien Gendre writes:
>> May you please elaborate?
>
> When a webpage is generated by `org-html-publish-to-html`, it put the
> title of the document at top of the HTML content as an .
>
> I wanted to modify it to put Author and date below this title but before
> the rest of the content.
For
On 09/05/2023 18:34, Ihor Radchenko wrote:
I can easily see Lualatex-specific preamble simply failing to work on
Latex. Or things being rendered wrongly.
iftex.sty has \ifpdftex and \iftutex (XeTeX, LuaTeX, LuaHBTeX) commands,
so it is possible to create universal preamble with some
Timothy writes:
> Hi Ihor,
>
>>> As a result of this issue (plus other issues with xelatex), I’m
>>> considering adding an option to specify different LaTeX compilers for
>>> previews and exports, with the default option continuing to be
>>> the value of `org-latex-compiler’.
>>
>> I am not
Hi Ihor,
>> To be clear, the default will be “use the same preview compiler as document
>> compiler”, but the hassles we’re currently experiencing with XeLaTeX/LuaLaTeX
>> make us think it could be worth adding an override option.
>
> I understand. I propose to fall back to the default even if
Timothy writes:
>> One option could be trying pdflatex first and falling back to the
>> default compiler on failure. But only as non-default option.
>
> To be clear, the default will be “use the same preview compiler as document
> compiler”, but the hassles we’re currently experiencing with
Ypo writes:
> Hi
>
> Is it possible to, each time I write "" to be subsituted by "[...]" ?
>
> I can't do it using abbrev, and I don't know how to do it using org-entities.
>
> I use it to yank quotes, for example, I write:
>
> "Like other editors, Emacs has commands to search for
Hi Ihor,
>> As a result of this issue (plus other issues with xelatex), I’m
>> considering adding an option to specify different LaTeX compilers for
>> previews and exports, with the default option continuing to be
>> the value of `org-latex-compiler’.
>
> I am not sure if it is a good idea.
> I
Hi
Is it possible to, each time I write "" to be subsituted by "[...]" ?
I can't do it using abbrev, and I don't know how to do it using
org-entities.
I use it to yank quotes, for example, I write:
"Like other editors, Emacs has commands to search for occurrences of
a string.
Karthik Chikmagalur writes:
> As a result of this issue (plus other issues with xelatex), I'm
> considering adding an option to specify different LaTeX compilers for
> previews and exports, with the default option continuing to be
> the value of `org-latex-compiler'.
I am not sure if it is a
> On Mon, 8 May 2023 at 18:35, Uwe Brauer wrote:
> I think this is the package we are referring to?
> https://github.com/larstvei/ox-gfm
Thanks very much
> https://list.orgmode.org/m2eh1adtye@ifi.uio.no/
> The README says loading ox-gfm adds it to the org-export-dispatch, I
> tried doing
"Thomas S. Dye" writes:
>> Which likely means that something is calling folding functions
>> from
>> outline.el instead of Org-native folding.
>
> Excellent!
>
> Would it be useful for me to search for calls to the folding
> functions from outline.el in the source code of the Org packages
>
Just another check on my side for any appearance of "org-fold-": Nothing in
my code, only org related packages use it.
$ grep -r -l org-fold- .
./org/.git/index
./org/doc/org-manual.org
./org/etc/ORG-NEWS
./org/lisp/ob-core.el
./org/lisp/ob-exp.el
./org/lisp/ob-lilypond.el
./org/lisp/ob-ref.el
bvchg...@mail.com writes:
> I'm attempting my first non-trivial elisp and seem to be falling at the
> first hurdle.
>
> Specifically, I am using (org-trigger-hook) to inspect a TODO->DONE state
> change, and am finding that the note that I insert when the state change
> is logged is not present
Hi all,
I'm attempting my first non-trivial elisp and seem to be falling at the
first hurdle.
Specifically, I am using (org-trigger-hook) to inspect a TODO->DONE state
change, and am finding that the note that I insert when the state change
is logged is not present in the result of a call to
Ihor Radchenko writes:
"Thomas S. Dye" writes:
You can try
M-x debug-on-variable-change org-fold-core-style
In case it's helpful, I set debug-on-variable-change as you
suggested but was bitten by the bug without triggering the
debugger.
Which likely means that something is calling
Michael Dauer writes:
> What could be called. It's not org-fold-core-style.
I am not really sure.
In order to avoid these situations Org advices `outline-flag-region'.
But something may apply outline overlays bypassing that function, in theory.
> Can I be just a data corruption of the text
What could be called. It's not org-fold-core-style.
Can I be just a data corruption of the text properties? I've no idea what
they are exactly, and what other parts use them. Maybe a conflicting key,
or failed optimization, or side effect on the regions they apply to. I just
want to give ideas
"Thomas S. Dye" writes:
>> You can try
>> M-x debug-on-variable-change org-fold-core-style
>
> In case it's helpful, I set debug-on-variable-change as you
> suggested but was bitten by the bug without triggering the
> debugger.
Which likely means that something is calling folding functions
27 matches
Mail list logo
