On 3/8/23 20:38, Bruno Barbier wrote:
Hi Zelphir,
Zelphir Kaltstahl writes:
On 3/7/23 20:52, Bruno Barbier wrote:
Also thanks for the idea with sessions + separate import source block. I thought
that should work, but apparently that also has the same error, when running for
the first time:
On Wednesday, 8 March 2023 20:14:53 CET Bruno Barbier wrote:
>
> Hi Chris,
>
> chris writes:
>
> > On Thursday, 2 March 2023 20:00:14 CET Bruno Barbier wrote:
> >> The behavior looks the same using only text-mode (without using org).
> >> You should probably report this as an Emacs bug (see
Ihor Radchenko writes:
> net-utils.el also has "*ftp [host]*". Notably, with space.
> I found no other use of [...] in Emacs sources.
Looking at my buffers, I see:
- e.g. "FILE" from Project.el
- e.g. "*EGLOT (PROJECT/(MODE)) events*" from Eglot
- e.g. "magit-diff(FILE1 -- FILE2): PROJECT"
Hi Zelphir,
Zelphir Kaltstahl writes:
> On 3/7/23 20:52, Bruno Barbier wrote:
> Also thanks for the idea with sessions + separate import source block. I
> thought
> that should work, but apparently that also has the same error, when running
> for
> the first time:
>
> ...
Oh, I see. I
Hi Chris,
chris writes:
> On Thursday, 2 March 2023 20:00:14 CET Bruno Barbier wrote:
>> The behavior looks the same using only text-mode (without using org).
>> You should probably report this as an Emacs bug (see M-x
>> report-emacs-bug).
>
> What command for latex preview in text mode?
BTW,
for listings, this seems to help with the backslashes
\usepackage{upquote}
\newcommand{\BSL}{\char`\\}
Best, /PA
On Wed, 8 Mar 2023 at 16:14, Rob Sargent wrote:
>
>
>
> > On Mar 8, 2023, at 3:09 AM, Pedro Andres Aranda Gutierrez
> > wrote:
> >
> > On 3/6/23 Rob Sargent wrote:
> >
>
On Tue, 2023-03-07 at 22:31 +0700, Max Nikulin wrote:
> On 06/03/2023 10:17, lux wrote:
> > On Sat, 2023-02-18 at 11:43 +, Ihor Radchenko wrote:
> > >
> > > I think should be (rename-file img-out out-file t)
> >
> > Fixed, thank you.
>
> There are a couple more mv shell commands in
On 26/02/2023 06:32, Samuel Wales wrote:
i acccomplished this with (define-key org-mode-map (quote [C-tab])
(quote org-next-link)) [kbd would be better].
...
i.e. like m-. on a function name, if that is set up to work, or c-h f
command tab ret to go to the fuction definition, but for keys.
I
> On Mar 8, 2023, at 7:59 AM, Max Nikulin wrote:
>
> On 08/03/2023 07:29, Rob Sargent wrote:
>>> LuaLaTeX may be instructed to use fallback fonts, see e.g.
> ...
>>> To my taste it is too low level.
>> That I placed the unicode into the text was "too low level"? I could argue
>> that "it's
> On Mar 8, 2023, at 3:09 AM, Pedro Andres Aranda Gutierrez
> wrote:
>
> On 3/6/23 Rob Sargent wrote:
>
>> I think I have to decide on one format and stick with it. I get bitten
>> by ODT/DOC transformations, not sure I like the default look of
>> LaTeX/pdf, HTML is pretty reliable but
On 07/03/2023 20:59, Ihor Radchenko wrote:
I agree about the last example, but what about "Heading [0/1] text"?
Both "Heading" and "[0/1]" have the same :post-blank " ", so when
stripping the statistics cookie use " " :post-blank for "Heading"
(retain current value).
Max Nikulin writes:
On 08/03/2023 07:29, Rob Sargent wrote:
LuaLaTeX may be instructed to use fallback fonts, see e.g.
...
To my taste it is too low level.
That I placed the unicode into the text was "too low level"? I could
argue that "it's a UTF doc", or that "\ding{55}" is bizarrely high
level. Other's
Rudolf Adamkovič writes:
> Ihor Radchenko writes:
>
>> Could you elaborate about "more standard"?
>
> Sure. For example, when I look at my Mode Line now, I see that the major more
> is "Message[Notmuch]". When I look at the names of the currently open
> buffers,
> I see "FOO" and "{FOO}" and
Jean Louis writes:
>> > Here is suggestion:
>> > ---
>> >
>> > 1. Convert local time timestamp to UTC
>> > 2. Add 10024 hours
>> > 3. Provide timestamp in UTC
>>
>> This will involve converting time, which is prone to errors. I still
>> think that sometimes it is more convenient
On 3/6/23 Rob Sargent wrote:
> I think I have to decide on one format and stick with it. I get bitten
> by ODT/DOC transformations, not sure I like the default look of
> LaTeX/pdf, HTML is pretty reliable but not best for handing out. Maybe
> I'll go back to "text" and call it good.
If my .2
Zelphir Kaltstahl writes:
> Actually, now that I think about it, the whole problem is gone, when
> replacing
> the wrapping let with 2 separate (define ...), which I originally thought org
> would do:
> ...
> Is there a reason it has to be wrapped in a let, instead of simply define-ing
> the
16 matches
Mail list logo
