unofficial mirror of bug-gnu-emacs@gnu.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: Tue, 12 Jul 2022 14:04:55 +0800	[thread overview]
Message-ID: <874jzm7to8.fsf@localhost> (raw)
In-Reply-To: <871qurnf0d.fsf@gnu.org>

Roland Winkler <winkler@gnu.org> writes:

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

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.

As for using bibtex-string-files in my specific scenario, I cannot make
it work as well.

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

Also, note that bibtex-string-files cannot help with situations when the
BibTeX buffer does not have an associated file.

Best,
Ihor





  reply	other threads:[~2022-07-12  6:04 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 [this message]
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=874jzm7to8.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 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).