Pedro Andres Aranda Gutierrez writes:
> I'll push the change is a couple of minutes.
Thanks!
Note that you should also go through the manual and adjust LANGUAGE
keyword description everywhere.
Also, :languages is an "export option" (`org-export-options-alist').
--
Ihor Radchenko // yantar92,
No worries. In a group with native and non-native speakers, it is
always the case that we all need clarifications.
That been part of my life since I was 3 ;-)
Add to this "life" and it is more than possible that someone (in this
case yours truely) reads more into a message that there really is,
so
Pedro Andres Aranda Gutierrez writes:
> Just to clarify. Your initial suggestion was having :languages in
> LaTeX only and use :language for the first and :languages for all.
> Now you want to have this behaviour for all backends (except that the
> others only use :language FTMB).
Likely not.
My
Just to clarify. Your initial suggestion was having :languages in
LaTeX only and use :language for the first and :languages for all.
Now you want to have this behaviour for all backends (except that the
others only use :language FTMB).
So I just change the entry, all backends allow more than one la
After writing the loeb function in Emacs Lisp recently, it occurs to me that
it could be used to write an evaluation function for Org spreadsheet tables
that is both maximally efficient (in that no cell is calculated twice) and
always converges on a stable end result. The steps are as follows:
1.
suzume writes:
> I’m looking for users of org-publish to have ideas on possible configurations
> and tweaks.
>
> I understand that recent CSS can do marvels on any kind of structure, but I’m
> looking for ways to have tags, for ex., and other tools that are available in
> other static site gen
Jonas Großekathöfer via "General discussions about Org-mode."
writes:
> ~org-blank-before-new-entry~ does also not work as expected for me using
> ~org-capture~. However, I would like to HAVE blank lines for new
> entries. But this setting takes only affect within the date tree (see
> below):
Derek Chen-Becker writes:
> I guess looking at https://orgmode.org/manual/Priorities.html, it's not
> clearly defined what valid ranges are. Are upper and lower cases considered
> equivalent? Is it strictly A-Z, or a-z, or 1-64? If it's not numeric, do
> we just allow any character whose value is
I guess looking at https://orgmode.org/manual/Priorities.html, it's not
clearly defined what valid ranges are. Are upper and lower cases considered
equivalent? Is it strictly A-Z, or a-z, or 1-64? If it's not numeric, do
we just allow any character whose value is >= 65? For example, 一，二， 三， 四?
Tech
OK, will do after the IETF,
/PA
On Sat, 19 Jul 2025 at 15:59, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > I've moved the change in the behaviour of #+LANGUAGE to the creaking
> > changes section and expanded it a bit.
>
> I do not like the idea of changing the meaning o
Pedro Andres Aranda Gutierrez writes:
> {{{clp}}} is shorter and comfier to write than \clearpage (at least
> for me TM)...
> The other one is for me to highlight things that are LaTeX (as opposed
> to pure Org).
> Just a question like ... would it make sense to have an org construct for
> this?
Pedro Andres Aranda Gutierrez writes:
> {{{clp}}} is shorter and comfier to write than \clearpage (at least
> for me TM)...
> The other one is for me to highlight things that are LaTeX (as opposed
> to pure Org).
> Just a question like ... would it make sense to have an org construct for
> this?
{{{clp}}} is shorter and comfier to write than \clearpage (at least
for me TM)...
The other one is for me to highlight things that are LaTeX (as opposed
to pure Org).
Just a question like ... would it make sense to have an org construct for this?
But you are right...
/PA
On Sat, 19 Jul 2025 at 16
"Rohit Patnaik" writes:
> I looked up Captain mode and it seems like the problem is that the default
> sentence start function =(car (bound-of-thing-at-point 'sentence))= finds the
> list marker as the start of the given sentence.
>
> It is possible to override that behavior. The mode defines a v
Benjamin McMillan writes:
> When archiving a subtree to a different heading in the same buffer, all
> headings are unfolded and the current narrowing is lost. This is easily
> reproduced in a minimal instance of emacs by the following steps:
>
> 1. In an org file, create two headings "head" and "
Hi Pedro.
I tried what you said, but I couldn't get it to work. I switched to the
feature/all-tex-fonts branch for org and compiled org, but I still got the
same error. Perhaps I didn't do this correctly.
On Sat, 19 Jul 2025 at 11:34, Pedro Andres Aranda Gutierrez <
paag...@gmail.com> wrote:
> A
Pedro Andres Aranda Gutierrez writes:
> Attached is the org file.
The file works on my side as well.
Aside:
Why #+MACRO: clp @@latex: \clearpage@@
and why @@latex: \normalfont{@@ பொருள் @@latex: }@@?
You can just write \clearpage or
\normalfont{பொருள்}
Both are perfectly valid as latex-fragme
Pedro Andres Aranda Gutierrez writes:
> I would like to be a bit more pragmatic in our approach:
> The question I would like to ask us all is whether the feature branch
> handles more situations than the current implementation.
> If that is the case, why not go ahead and integrate it into master?
Derek Chen-Becker writes:
> I'm also not clear on why we upcase again when checking the bounds:
>
> ((or (< (upcase new) org-priority-highest) (> (upcase new)
> org-priority-lowest))
That's a historical code. It has been there before the earlier upcase
was introduced.
Here is the initial versio
Pedro Andres Aranda Gutierrez writes:
> I've moved the change in the behaviour of #+LANGUAGE to the creaking
> changes section and expanded it a bit.
I do not like the idea of changing the meaning of #+LANGUAGE *just for
ox-latex*. Instead, let's change ox.el itself.
(You current code implements
Sure, but there's the check in the let to set `nump' based on the
highest/lowest priority. I could add that as a condition to the upcase
transform:
(when (and (= (upcase org-priority-highest) org-priority-highest)
(= (upcase org-priority-lowest) org-priority-lowest)
Derek Chen-Becker writes:
> Just double-checking my understanding of things, but it looks like
> `org-priority' already handles number inputs, despite the docstring:
>
> ((or (eq action 'set)
> (integerp action))
> (if (not (eq action 'set))
> (setq
Just double-checking my understanding of things, but it looks like
`org-priority' already handles number inputs, despite the docstring:
((or (eq action 'set)
(integerp action))
(if (not (eq action 'set))
(setq new action)
My read of that is that if t
Ihor Radchenko writes:
>> org--warnings '("org-element--cache: Org parser error in
>> perso.org::#. Resetting.\n The error was:
>> (error \"Invalid search bound (wrong side of point)\")\n Backtrace:\nnil\n
>> Please report this to Org mode mailing list (M-x org-submit-bug-report)."
>> "org-e
Ihor Radchenko writes:
> This variable only affects fontification.
> The Org markup is not customizeable for emphasis.
> We will likely obsolete and remove this variable in the future.
I tried to make the docstring more clear about this.
Fixed, on bugfix.
https://cgit.git.savannah.gnu.org/cgit/e
suzume writes:
> I’m looking for users of org-publish to have ideas on possible configurations
> and tweaks.
>
> I understand that recent CSS can do marvels on any kind of structure, but I’m
> looking for ways to have tags, for ex., and other tools that are available in
> other static site gen
Hi Pedro.
> I've come up with a solution, which is to customise the mode the
export buffer is opened with. You could set it to plain latex-mode
instead of LaTeX-mode. This will disable auctex functionality. Would
that be an issue for you?
I don't see that being a problem.
> If you are interested
27 matches
Mail list logo
