emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy <tecosaur@gmail.com>
To: Matt Huszagh <huszaghmatt@gmail.com>
Cc: Ihor Radchenko <yantar92@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix caption format for custom latex src block
Date: Wed, 29 Jun 2022 23:26:33 +0800	[thread overview]
Message-ID: <87pmir7ao9.fsf@gmail.com> (raw)
In-Reply-To: <87zghxtor2.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

Hi Matt,

As mentioned by Ihor, you’ll want to take a look at the curent version of
ox-latex, specifically `org-latex-src-block--custom' which now contains `(?c .
,caption)'. You may want to consider modifying `org-latex--caption/label-string' to
accept the form `(element info &optional content-only)' or reimplementing just the
bits needed for this purpose — which ever works out nicer. Looking at
`org-latex--caption/label-string' a substring approach looks quite fragile, though
you might be able to get away with an application of `replace-regexp-in-string',
though I’d personally consider this a bit of a last resort.

Matt Huszagh <huszaghmatt@gmail.com> writes:

> Ihor Radchenko <yantar92@gmail.com> writes:
>> I think that it will be better if you use
>> org-latex–caption/label-string instead. It will take care about short
>> captions as well.
> Changing this to (?c . ,caption-str) yields for the original example
> {Perform inter-sample interpolation.
> }
> I could use substring to remove the leading { and trailing
> }. What do you think?

All the best,

  parent reply	other threads:[~2022-06-29 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30  4:05 [PATCH] Fix caption format for custom latex src block Matt Huszagh
2022-06-14  3:51 ` Ihor Radchenko
2022-06-28  4:07   ` Matt Huszagh
2022-06-29  2:24     ` Ihor Radchenko
2022-06-29 15:20       ` Timothy
2022-06-29 15:26     ` Timothy [this message]
2022-07-09  0:23       ` Matt Huszagh
2022-07-31  4:03 ` Ihor Radchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmir7ao9.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=huszaghmatt@gmail.com \
    --cc=yantar92@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).