From: Eli Zaretskii <eliz@gnu.org>
To: Mekeor Melire <mekeor@posteo.de>,
kyle_jones@wonderworks.com, bwarsaw@python.org
Cc: 74970@debbugs.gnu.org
Subject: bug#74970: Supercite sc-setup-filladapt accesses void variable filladapt-prefix-table (from Filladapt)
Date: Sat, 04 Jan 2025 13:34:06 +0200 [thread overview]
Message-ID: <86sepyertd.fsf@gnu.org> (raw)
In-Reply-To: <87msgr29yn.fsf@posteo.de> (message from Mekeor Melire on Thu, 19 Dec 2024 11:22:56 +0000)
Ping! Barry and Kyle, could you please chime in?
> Cc: Kyle E. Jones <kyle_jones@wonderworks.com>,
> Barry A. Warsaw <bwarsaw@python.org>
> From: Mekeor Melire <mekeor@posteo.de>
> Date: Thu, 19 Dec 2024 11:22:56 +0000
>
> (Supercite is a built-in package and Filladapt is on GNU Elpa.)
> Supercite's manual [1] states that one can install Filladapt and
> call the `sc-setup-filladapt' function. But calling
> `sc-setup-filladapt' will result in the error (void-variable
> filladapt-prefix-table).
>
> It seems like Filladapt has renamed that variable from
> "filladapt-prefix-table" to "filladapt-token-table". I only found
> one very old version of Filladapt [2] where the old name is used.
>
> Apparently, the variable has not only been renamed but the logic
> of has changed quite a bit. For example, filladapt-prefix-table
> had the format ((REGXP . FUNCTION) ...) while
> filladapt-token-table has the format ((REGEXP SYM) ...).
>
> I'm CCing the authors of both packages.
>
> [1] (info "(sc) Filling Cited Text")
>
> [2] https://www.ic.unicamp.br/~stolfi/EXPORT/elisp/JUNK/mandel-disabled/filladapt.el
>
>
>
>
prev parent reply other threads:[~2025-01-04 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 11:22 bug#74970: Supercite sc-setup-filladapt accesses void variable filladapt-prefix-table (from Filladapt) Mekeor Melire
2025-01-04 11:34 ` Eli Zaretskii [this message]
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=86sepyertd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74970@debbugs.gnu.org \
--cc=bwarsaw@python.org \
--cc=kyle_jones@wonderworks.com \
--cc=mekeor@posteo.de \
/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).