all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Roland Winkler <winkler@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 56475@debbugs.gnu.org
Subject: bug#56475: 28.1.50; bibtex-parse-entry disregards @string substitutions
Date: Sun, 17 Jul 2022 16:34:02 +0800	[thread overview]
Message-ID: <87zgh887et.fsf@localhost> (raw)
In-Reply-To: <87pmial54o.fsf@gnu.org>

Roland Winkler <winkler@gnu.org> writes:

> On Tue, Jul 12 2022, Ihor Radchenko wrote:
>> I am wondering why bibtex-string-files is not documented inside the
>> docstring of bibtex-expand-strings. Same for bibtex-expand-strings not
>> being documented in bibtex-parse-entry.
>
> I believe the situation is the other way round: bibtex-files and
> bibtex-string-files are basic user variables for bibtex-mode and have
> been around for 30+ years (much longer than I support bibtex.el).
> bibtex-expand-strings is a small add-on in this context.

I think that the main issue on my side is that I interact with bibtex.el
from API perspective without editing many actual .bib files. So, I was
mostly looking into parser API instead of user customizations.

If you start exploring bibtex.el from bibtex-parse-entry and its
docstring, it is not very easy to figure out that bibtex-string-files
and bibtex-expand-strings need to be set. They are not mentioned in the
docstring other than by common word "extract content" with "extract"
meaning being not very clear.

>> I tried the following simple test:
>>
>> M-: (let ((bibtex-string-files `(,(buffer-file-name)))
>> (bibtex-expand-strings t)) (bibtex-parse-entry))
>>
>> The journal field is still not handled: ("journal" . "jgr")
>
> Try
>
> M-: (let ((bibtex-string-files `(,(buffer-file-name)))
> (bibtex-expand-strings t)) (bibtex-parse-entry t))

Thanks! It works now.

>> Also, note that bibtex-string-files cannot help with situations when
>> the BibTeX buffer does not have an associated file.
>
> When does this happen?  To the best of my knowledge, this has never been
> an issue for users of bibtex.el.

It is more of a hypothetical scenario that might occur in future if Org
tries to support bibliographies provided inside .org files. Such
bibliographies will need to be converted to .bib files transiently and
might not need to be saved on disk.

In any case, it is not a concern you need to worry about now. AFAIU,
bibtex.el depends on .bib buffers having non-nil buffer-file-name in
multiple places.

Best,
Ihor





  reply	other threads:[~2022-07-17  8:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10  7:14 bug#56475: 28.1.50; bibtex-parse-entry disregards @string substitutions Ihor Radchenko
2022-07-11 10:16 ` Lars Ingebrigtsen
2022-07-11 17:12   ` Roland Winkler
2022-07-11 17:29     ` Roland Winkler
2022-07-12  2:32       ` Ihor Radchenko
2022-07-12  4:14         ` Roland Winkler
2022-07-12  6:04           ` Ihor Radchenko
2022-07-12 15:31             ` Roland Winkler
2022-07-17  8:34               ` Ihor Radchenko [this message]
2022-07-17 20:10                 ` Roland Winkler
2022-07-18  4:07                   ` Ihor Radchenko
2022-12-30  6:37                     ` Roland Winkler

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=87zgh887et.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=56475@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=winkler@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.