On 12/04/2025 21:28, Ihor Radchenko wrote:
% = UNIVERSAL FALLBACK STACK =
% (Only activates when default font lacks glyphs)
\directlua{
luaotfload.add_fallback("global_fallback", {
"Noto Serif:mode=harf;", % 1st: Broad Unicode coverage
"DejaVu Serif:mode=harf;", % 2nd
Hi Ihor,
Use case: blank org-document where I was documenting a procedure for my
students in real-time (as I was showing them how to do it).
Once everything had been checked, I started adding the different
#+L̀ATEX... keywords. I didn't have any autocompletion for them.
Exiting emacs and reopening
Ihor Radchenko wrote:
> I am unable to reproduce without emacs -Q and with Org main branch on my
> side. Here is what I did:
> 1. Saved your example file to /tmp/test.org
> 2. Ran chmod -w /tmp/test.org && /home/yantar92/Git/emacs/src/emacs
> --init-directory=/tmp -L /home/yantar92/Git/org-mode/
On 10/04/2025 23:44, Pedro Andres Aranda Gutierrez wrote:
Thu, 10 Apr 2025 21:55:53 +0700 Max Nikulin
My conclusion from earlier discussions is that it is a challenge to
configure fonts to a given user document. It may contain (besides
latin-1) Greek, Cyrillic, CJK, emoji.
My experience is th
On 12/04/2025 21:11, Leo Butler wrote:
I use a lot of
utf-8 in my org documents. Pdflatex just cannot compete for typesetting,
even in preview.
Certainly PdfTeX has enough limitations. I am curious however what
specific issues you have faced (languages/scripts, character categories,
etc.)? Ma
Ihor Radchenko writes:
> David Masterson writes:
>
>> Interesting. My elisp is not strong, so a few questions:
>>
>> 1. Are you saying attr_all does not exist in Org and this code is
>>creating it?
>
> Anything in the form of #+attr_ is treated by Org mode as
> affiliated keyword. This keywo
> Thanks!
> May you attach the patch as a separate attachment next time?
> I was not able to apply this email patch automatically.
Sorry, I'm apparently not used to reading issue threads outside of Github. I
read too fast and missed everything after this.
>>> Adding back standard properties to
Pedro Andres Aranda Gutierrez writes:
> Since the block keywords are always the same, why not put them in a
> variable.
Sure. Thanks for the patch!
> Plus add the LATEX keywords, which seem not to want to appear in pcomplete
As discussed in
https://list.orgmode.org/orgmode/cao48bk-nbhy0thdj57_
Pedro Andres Aranda Gutierrez writes:
> A new version of the patch, including a test for the new
> #+BEAMER_CLASS_OPTIONS
Thanks!
I have no objections to adding a new keyword.
See my comments inline on the patch itself.
> Subject: [PATCH] New BEAMER_CLASS_OPTIONS
>
> * lisp/ox-beamer.el: Add #+
ian martins writes:
> org exports to markdown automatically rename links to org files as
> links to md files. It's not possible to link to an org file and have
> it remain an org file in the exported markdown.
>
> org exports to html do the same thing but have an option to disable
> this mapping
Pedro Andres Aranda Gutierrez writes:
> in the meantime, here is a (somehow egoistic?) patch that adds the latex
> keyworks I need
> ...
> ( pcomplete/org-mode/file-option): import ox-latex to include
> LaTeX keywords in completion logic
Sorry, but no.
What you suggest is not much different fro
Lei Zhe writes:
>> how can users of `org-babel-tangle-single-block' figure out which variant of
>> the return value is to expect?
> It returns the correct relative or absolute link that users can expect
> when :tangle is a single path, while it returns an absolute link when
> :tangle is a list.
Hi,
in the meantime, here is a (somehow egoistic?) patch that adds the latex
keyworks I need
Best, /PA
On Sat, 12 Apr 2025 at 18:56, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > So, maybe we should include
> > '(require ox-latex)
> > in pcomplete to get the LaTeX keywo
Pedro Andres Aranda Gutierrez writes:
> So, maybe we should include
> '(require ox-latex)
> in pcomplete to get the LaTeX keywords
I do not think so.
If we were to do it, we would also need to load all other export
backends. And that would entitle loading all export backends on startup.
Startup
But is your local stylesheet uploaded to the server, as it has to be for
the stylesheet link in your HTML head to locate it? That's what Rohit
was getting at, I think.
Apologies if this is obvious and your problem is a different one, but
it's not clear from your reply. You say that a link to a rem
Pedro Andres Aranda Gutierrez writes:
> Hmmm... I don't get it.
> If I have #+STARTUP: beamer, I get the beamer keywords and there is no
> (require 'ox-beamer)
> in org-pcomplete.el
>
> But if I want to have the latex keywords, I need
> (require 'ox-latex)
> I'm a bit puzzled ... sorry
#+STARTUP
Ihor Radchenko writes:
> Thanks! The logic is not ideal, but babel is not ideal in general, so
> let's not worry too much about various edge cases. The patch is an
> improvement over the existing state of affairs anyway.
>
> Feel free to push.
Thanks, I've pushed to main now. Agree it's not idea
Hi Leo
not suggesting anything... just exploring alternatives. I too have a lot of
UTF-8 in my
documents and pdf-latex chokes at them, too.
I'm not using preview -have never been- because my field of research didn't
need complex
math in my papers.
Thanks for your feedback :-)
/PA
On Sat, 12 Apr 2
"Pedro A. Aranda" writes:
> 0001 is a trivial way to clarify the warning about unsupported fonts
> with a more 'blunt' language. This is what I said could go as a bug fix.
Installed.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=066952da0b
I removed the news entry as this chan
On Thu, Apr 10 2025, Pedro Andres Aranda Gutierrez wrote:
> Jürgen writes:
>
>>Am 03.04.25 um 09:37 Uhr schrieb Ihor Radchenko:
I don't agree. Users who are apparently happy with LuaLaTeX should
have no problems with pdflatex and UTF8.
>>> If you know an easy and universal way to suppor
Sébastien Gendre writes:
> A third solution would be to add a search feature to Org-mode, that
> could be used from Org-mode and exported in HTML.
> ...
> # Step 1: Search feature in Org-mode only
> ...
> # Step 2: Add HTML export of the search feature
> ...
> # Step 3: An option in org-publish t
Sébastien Gendre writes:
> # Solution 1
>
> After looking at Pagefind, I was thinking of taking inspiration from
> "org-export-define-backend".
>
> Creating a function named like "org-html-define-search-engine" and that
> will have as parameters:
> ...
This looks reasonable and flexible. +1
>
Rudolf Adamkovič writes:
> Here are some things we could do...
>
> OPTION 1: Keep it simple, if a bit messy:
>
> Rename `org-texinfo-listings-langs' to `org-texinfo-langs', and make
> sure all languages Org supports OOTB map correctly to Highlight,
> Pygments, and GNU Source Highlight. Per
"Rohit Patnaik" writes:
>> Why "5"?
>
> That accounts for the spaces and parentheses surrounding the headline. I've
> updated the code to use a variable (`spaces-and-parens-length') for that
> instead.
This does not eliminate the problem with magic constant in the code.
If we ever change the exa
Mike Kupfer writes:
> Ihor Radchenko wrote:
>
>> I can reproduce. However, I cannot reproduce on the latest bugfix and on
>> the latest main. Try to upgrade Org mode and let me know if you keep
>> seeing the problem.
>
> I tried 9.7.27 (latest available from GNU ELPA) and main (downloaded
> today
Pedro Andres Aranda Gutierrez writes:
> [PATCH]: add #+latex... and #+beamer...
>
> Just in case, I'm adding a small patch to add the missing keywords I miss
> when editing org to export to latex and beamer.
Thanks, but I do not think that such manual listing of backend options
is future-proof.
26 matches
Mail list logo
