On Wed, 14 Jul 2021 20:43:24 -0400 John Kitchin wrote:
> Hi all, I could use a bit of help with a regexp. I am trying to fine tune the
> org-ref citation regexp to
> make it orthogonal to org-cite.
>
> I want to recognize these as org-ref links
>
> [[cite:schuett-2018-schnet]]
>cite:schuett-
On Thu, 15 Jul 2021 10:40:40 +0200 Stephen Berman
wrote:
> On Wed, 14 Jul 2021 20:43:24 -0400 John Kitchin
> wrote:
>
>> Hi all, I could use a bit of help with a regexp. I am trying to fine tune
>> the org-ref citation regexp to
>> make it orthogonal to org-cite.
>>
>> I want to recognize the
>>> "a" == autofrettage writes:
> Hi,
> Uwe wrote:
>> I am not entirely convinced by this mode and now came across
>> virtual-auto-fill-mode that looks to me a much nicer solution.
>> Any comments?
> I haven't tried virtual-a-f-m myself, so I cannot say if it is
> the ultimate solution. Howeve
Tim Cross writes:
> Stefan Nobis writes:
>> But maybe we could assemble a list of good (enough) fonts for
>> different languages/scripts and provide a default setup in Org for
>> LaTeX export, that sets a proper font for the chosen document
>> language?
> I think such a list would be a really g
Thanks everyone, these are all good suggestions.
I realized though the problem is that org-mode is recognizing something
like [cite:@darby-2018-lonel-atoms] as a cite link because of the cite:
part of it. In fact org-mode seems to recognize all [link:path] as an
org link.
In general that seems ok
On 15/07/2021 02:05, Stefan Nobis wrote:
Maxim Nikulin writes:
There are cm-super fonts for at least of 15 years.
There are many tradeoffs in many aspects. No single font pleases
everyone. So you want to say: Your requirements are more
important/common/stylish/whatever that the requirements o
Hi,
The async pdf export functionality appears to be broken with latest org
and a
recent emacs version compiled with native-comp enabled (I have not tested
without native-comp).
To reproduce:
- use `emacs -q` and an empty init.el file (your init file gets picked
up by
the async emacs in
Maxim Nikulin writes:
> In CSS it is possible to specify a list of fonts and a glyph is taken
> from the first font where it is present. Despite particular fonts have
> limited coverage, I see wide range of Unicode characters on web pages,
> that is why I am almost sure that system font libraries
Sébastien Miquel writes:
> Hi,
>
> The async pdf export functionality appears to be broken with latest org and a
> recent emacs version compiled with native-comp enabled (I have not tested
> without native-comp).
>
> To reproduce:
>
> - use `emacs -q` and an empty init.el file (your init file
> On Jul 15, 2021, at 10:45 AM, Sébastien Miquel
> wrote:
>
> Hi,
>
> The async pdf export functionality appears to be broken with latest org and a
> recent emacs version compiled with native-comp enabled (I have not tested
> without native-comp).
>
> To reproduce:
>
> - use `emacs -q` an
> On Jul 15, 2021, at 4:05, Stefan Nobis wrote:
>
>> Is it possible to provide reasonable defaults for fonts?
>
> I do not think so. You want Cyrillic. But what about Japanese,
> Chinese, Devanagari, Tamil, Arabic etc? I doubt that there exists a
> single font that supports all these scripts
Mark Barton writes:
> I use native-comp, but have not tried the async export yet.
FWIW I use native-comp (with Doom + my config) and async PDF export
works.
--
Timothy
Timothy writes:
> Mark Barton writes:
>
>> I use native-comp, but have not tried the async export yet.
>
> FWIW I use native-comp (with Doom + my config) and async PDF export
> works.
It might be useful for the OP if you could post what commit of Emacs 28
you are running. Native compilation i
13 matches
Mail list logo
