unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Roland Winkler <winkler@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 56475@debbugs.gnu.org
Subject: bug#56475: 28.1.50; bibtex-parse-entry disregards @string substitutions
Date: Mon, 11 Jul 2022 23:14:58 -0500	[thread overview]
Message-ID: <871qurnf0d.fsf@gnu.org> (raw)
In-Reply-To: <87fsj76oxi.fsf@localhost> (Ihor Radchenko's message of "Tue, 12 Jul 2022 10:32:41 +0800")

On Tue, Jul 12 2022, Ihor Radchenko wrote:
> Roland Winkler <winkler@gnu.org> writes:
>
>> If I understand your issue correctly you probably want to let-bind the
>> user variable bibtex-expand-strings while calling bibtex-parse-entry so
>> that your code works irrespective of what users have chosen for
>> bibtex-expand-strings.
>
> Thanks for the pointer!
> I tried my reproducer by running
> M-: (let ((bibtex-expand-strings t)) (bibtex-parse-entry))
> instead of
> M-: (bibtex-parse-entry)
>
> Unfortunately, the journal field is still not substituted.

The variable bibtex-string-files tells bibtex.el where it can find the
string definitions (which are then stored in the variable
bibtex-strings).  This complements bibtex-files that tells bibtex.el
where it can find the BibTeX entries.  A command like
bibtex-search-entry searches the entries in the files in bibtex-files.





  reply	other threads:[~2022-07-12  4:14 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 [this message]
2022-07-12  6:04           ` Ihor Radchenko
2022-07-12 15:31             ` Roland Winkler
2022-07-17  8:34               ` Ihor Radchenko
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=871qurnf0d.fsf@gnu.org \
    --to=winkler@gnu.org \
    --cc=56475@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=yantar92@gmail.com \
    /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 public inbox

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

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).