GNU bug report logs -
#76131
30.0.93; vlf: advice for abort-if-file-too-large seems broken in Emacs 30
Previous Next
Reported by: fap <hello <at> fap.re>
Date: Fri, 7 Feb 2025 20:41:01 UTC
Severity: normal
Found in version 30.0.93
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 76131 in the body.
You can then email your comments to 76131 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Fri, 07 Feb 2025 20:41:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
fap <hello <at> fap.re>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 07 Feb 2025 20:41:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
After upgrading to Emacs 30 I couldn't open files anymore
with (vlf-setup) applied / required.
The backtrace is as follows:
Debugger entered--Lisp error: (void-variable always)
ad-Advice-abort-if-file-too-large(#f(compiled-function (size op-type
filename &optional offer-raw) "If file SIZE larger than
`large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
the file operation being performed (for message\nto user). If OFFER-RAW
is true, give user the additional option\nto open the file literally.
If the user chooses this option,\n`abort-if-file-too-large' returns the
symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
#<bytecode -0x118b121ca418257d>) 16007 "open"
"~/.local/share/chezmoi/emacs/github-pandoc.css" t)
apply(ad-Advice-abort-if-file-too-large #f(compiled-function (size
op-type filename &optional offer-raw) "If file SIZE larger than
`large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
the file operation being performed (for message\nto user). If OFFER-RAW
is true, give user the additional option\nto open the file literally.
If the user chooses this option,\n`abort-if-file-too-large' returns the
symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
#<bytecode -0x118b121ca418257d>) (16007 "open"
"~/.local/share/chezmoi/emacs/github-pandoc.css" t))
abort-if-file-too-large(16007 "open"
"~/.local/share/chezmoi/emacs/github-pandoc.css" t)
find-file-noselect("/home/fap/.local/share/chezmoi/emacs/github-pandoc.css"
nil nil t)
find-file("/home/fap/.local/share/chezmoi/emacs/github-pandoc.css" t)
funcall-interactively(find-file
"/home/fap/.local/share/chezmoi/emacs/github-pandoc.css" t)
call-interactively(find-file nil nil)
command-execute(find-file)
I looked at the code, but I don't really get how 'always could get
interpreted as a variable?
In GNU Emacs 30.0.93 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.41, cairo version 1.18.0) of 2025-02-07 built on T580
Repository revision: 6cfab9154ddec0adc5b8a6701019c9c066c3f9f9
Repository branch: pretest
System Description: Ubuntu 24.04.1 LTS
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Fri, 07 Feb 2025 21:15:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 76131 <at> debbugs.gnu.org (full text, mbox):
fap via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs <at> gnu.org> writes:
> After upgrading to Emacs 30 I couldn't open files anymore
> with (vlf-setup) applied / required.
For context, this bug report is about:
https://elpa.gnu.org/packages/vlf.html
Andrey, do you have any comments?
> The backtrace is as follows:
>
> Debugger entered--Lisp error: (void-variable always)
> ad-Advice-abort-if-file-too-large(#f(compiled-function (size op-type
> filename &optional offer-raw) "If file SIZE larger than
> `large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
> the file operation being performed (for message\nto user). If OFFER-RAW
> is true, give user the additional option\nto open the file literally.
> If the user chooses this option,\n`abort-if-file-too-large' returns the
> symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
> #<bytecode -0x118b121ca418257d>) 16007 "open"
> "~/.local/share/chezmoi/emacs/github-pandoc.css" t)
> apply(ad-Advice-abort-if-file-too-large #f(compiled-function (size
> op-type filename &optional offer-raw) "If file SIZE larger than
> `large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
> the file operation being performed (for message\nto user). If OFFER-RAW
> is true, give user the additional option\nto open the file literally.
> If the user chooses this option,\n`abort-if-file-too-large' returns the
> symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
> #<bytecode -0x118b121ca418257d>) (16007 "open"
> "~/.local/share/chezmoi/emacs/github-pandoc.css" t))
> abort-if-file-too-large(16007 "open"
> "~/.local/share/chezmoi/emacs/github-pandoc.css" t)
>
> find-file-noselect("/home/fap/.local/share/chezmoi/emacs/github-pandoc.css"
> nil nil t)
> find-file("/home/fap/.local/share/chezmoi/emacs/github-pandoc.css" t)
> funcall-interactively(find-file
> "/home/fap/.local/share/chezmoi/emacs/github-pandoc.css" t)
> call-interactively(find-file nil nil)
> command-execute(find-file)
>
> I looked at the code, but I don't really get how 'always could get
> interpreted as a variable?
>
> In GNU Emacs 30.0.93 (build 1, x86_64-pc-linux-gnu, GTK+ Version
> 3.24.41, cairo version 1.18.0) of 2025-02-07 built on T580
> Repository revision: 6cfab9154ddec0adc5b8a6701019c9c066c3f9f9
> Repository branch: pretest
> System Description: Ubuntu 24.04.1 LTS
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Sat, 08 Feb 2025 07:51:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 76131 <at> debbugs.gnu.org (full text, mbox):
> Date: Fri, 7 Feb 2025 21:39:45 +0100
> From: fap via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>
> After upgrading to Emacs 30 I couldn't open files anymore
> with (vlf-setup) applied / required.
>
> The backtrace is as follows:
>
> Debugger entered--Lisp error: (void-variable always)
> ad-Advice-abort-if-file-too-large(#f(compiled-function (size op-type
> filename &optional offer-raw) "If file SIZE larger than
> `large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
> the file operation being performed (for message\nto user). If OFFER-RAW
> is true, give user the additional option\nto open the file literally.
> If the user chooses this option,\n`abort-if-file-too-large' returns the
> symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
> #<bytecode -0x118b121ca418257d>) 16007 "open"
> "~/.local/share/chezmoi/emacs/github-pandoc.css" t)
> apply(ad-Advice-abort-if-file-too-large #f(compiled-function (size
> op-type filename &optional offer-raw) "If file SIZE larger than
> `large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
> the file operation being performed (for message\nto user). If OFFER-RAW
> is true, give user the additional option\nto open the file literally.
> If the user chooses this option,\n`abort-if-file-too-large' returns the
> symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
> #<bytecode -0x118b121ca418257d>) (16007 "open"
> "~/.local/share/chezmoi/emacs/github-pandoc.css" t))
> abort-if-file-too-large(16007 "open"
> "~/.local/share/chezmoi/emacs/github-pandoc.css" t)
>
> find-file-noselect("/home/fap/.local/share/chezmoi/emacs/github-pandoc.css"
> nil nil t)
> find-file("/home/fap/.local/share/chezmoi/emacs/github-pandoc.css" t)
> funcall-interactively(find-file
> "/home/fap/.local/share/chezmoi/emacs/github-pandoc.css" t)
> call-interactively(find-file nil nil)
> command-execute(find-file)
>
> I looked at the code, but I don't really get how 'always could get
> interpreted as a variable?
I cannot reproduce this. Does the problem happen if you load
vlf-setup.el manually, as a Lisp (not compiled) file?
Also, which version of vlf do you have?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Sat, 08 Feb 2025 13:05:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 76131 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Okay, I think that one was my bad, as I was using the unmaintained melpa
version.
But now I ran into another error in the same advice with the elpa
version 1.7.2.
This is the error I'm getting now:
Debugger entered--Lisp error: (void-variable size)
ad-Advice-abort-if-file-too-large(#f(compiled-function (size op-type
filename &optional offer-raw) "If file SIZE larger than
`large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
the file operation being performed (for message\nto user). If OFFER-RAW
is true, give user the additional option\nto open the file literally.
If the user chooses this option,\n`abort-if-file-too-large' returns the
symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
#<bytecode -0xa03b2ee7918250d>) 1210 "open" "~/.bash_aliases" t)
apply(ad-Advice-abort-if-file-too-large #f(compiled-function (size
op-type filename &optional offer-raw) "If file SIZE larger than
`large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
the file operation being performed (for message\nto user). If OFFER-RAW
is true, give user the additional option\nto open the file literally.
If the user chooses this option,\n`abort-if-file-too-large' returns the
symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
#<bytecode -0xa03b2ee7918250d>) (1210 "open" "~/.bash_aliases" t))
abort-if-file-too-large(1210 "open" "~/.bash_aliases" t)
find-file-noselect("~/.bash_aliases" nil nil t)
find-file("~/.bash_aliases" t)
funcall-interactively(find-file "~/.bash_aliases" t)
call-interactively(find-file nil nil)
command-execute(find-file)
> Does the problem happen if you load vlf-setup.el manually, as a Lisp
> (not compiled) file?
Not completely sure I understand you correctly, but this also happens
when I directly load the file via
~(load "~/.emacs.d/elpa/vlf-1.7.2/vlf-setup.el")~ instead of ~(require
'vlf-setup)~.
I don't see a "vlf-setup.elc" file in the "vlf-1.7.2" folder.
The error also happens when I start emacs with ~emacs -q~.
On 2/8/25 08:50, Eli Zaretskii wrote:
>> Date: Fri, 7 Feb 2025 21:39:45 +0100
>> From: fap via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors"<bug-gnu-emacs <at> gnu.org>
>>
>> After upgrading to Emacs 30 I couldn't open files anymore
>> with (vlf-setup) applied / required.
>>
>> The backtrace is as follows:
>>
>> Debugger entered--Lisp error: (void-variable always)
>> ad-Advice-abort-if-file-too-large(#f(compiled-function (size op-type
>> filename &optional offer-raw) "If file SIZE larger than
>> `large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
>> the file operation being performed (for message\nto user). If OFFER-RAW
>> is true, give user the additional option\nto open the file literally.
>> If the user chooses this option,\n`abort-if-file-too-large' returns the
>> symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
>> #<bytecode -0x118b121ca418257d>) 16007 "open"
>> "~/.local/share/chezmoi/emacs/github-pandoc.css" t)
>> apply(ad-Advice-abort-if-file-too-large #f(compiled-function (size
>> op-type filename &optional offer-raw) "If file SIZE larger than
>> `large-file-warning-threshold', allow user to abort.\nOP-TYPE specifies
>> the file operation being performed (for message\nto user). If OFFER-RAW
>> is true, give user the additional option\nto open the file literally.
>> If the user chooses this option,\n`abort-if-file-too-large' returns the
>> symbol `raw'. Otherwise,\nit returns nil or exits non-locally."
>> #<bytecode -0x118b121ca418257d>) (16007 "open"
>> "~/.local/share/chezmoi/emacs/github-pandoc.css" t))
>> abort-if-file-too-large(16007 "open"
>> "~/.local/share/chezmoi/emacs/github-pandoc.css" t)
>>
>> find-file-noselect("/home/fap/.local/share/chezmoi/emacs/github-pandoc.css"
>> nil nil t)
>> find-file("/home/fap/.local/share/chezmoi/emacs/github-pandoc.css" t)
>> funcall-interactively(find-file
>> "/home/fap/.local/share/chezmoi/emacs/github-pandoc.css" t)
>> call-interactively(find-file nil nil)
>> command-execute(find-file)
>>
>> I looked at the code, but I don't really get how 'always could get
>> interpreted as a variable?
> I cannot reproduce this. Does the problem happen if you load
> vlf-setup.el manually, as a Lisp (not compiled) file?
>
> Also, which version of vlf do you have?
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Sat, 08 Feb 2025 13:54:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 76131 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 8 Feb 2025 14:04:05 +0100
> Cc: 76131 <at> debbugs.gnu.org
> From: fap <hello <at> fap.re>
>
> Okay, I think that one was my bad, as I was using the unmaintained melpa version.
> But now I ran into another error in the same advice with the elpa version 1.7.2.
>
> This is the error I'm getting now:
>
> Debugger entered--Lisp error: (void-variable size)
> ad-Advice-abort-if-file-too-large(#f(compiled-function (size op-type filename &optional offer-raw) "If file SIZE
I get no error at all with the version 1.7.2 on ELPA.
So I suspect some problem with outdated files on your system. Please
make sure you don't have old vlf files lying around, and that you only
use the *.el files from the latest version 1.7.2.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Sun, 09 Feb 2025 13:06:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 76131 <at> debbugs.gnu.org (full text, mbox):
fap via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs <at> gnu.org> writes:
> Okay, I think that one was my bad, as I was using the unmaintained melpa
> version.
Maybe someone could ask the MELPA maintainers to remove that outdated
package?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Sun, 09 Feb 2025 14:58:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 76131 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I had the stale version installed from MELPA myself so I installed the ELPA
version and it looks like package reported the incorrect path name but
under the covers did the right thing.
"Package vlf is installed.
Status: Installed in 'vlf-20191126.2250/'. <<<---- incorrect path: it
was put in vlf-1.7.2/
Version: 20191126.2250
Commit: cc02f2533782d6b9b628cec7e2dcf25b2d05a27c
Summary: View Large Files.
Website: https://github.com/m00natic/vlfi
Keywords: large files utilities
Other versions: 1.7.2 (installed), 20191126.2250 (melpa), 1.7.2 (gnu)."
On Sun, Feb 9, 2025 at 8:06 AM Stefan Kangas <stefankangas <at> gmail.com> wrote:
> fap via "Bug reports for GNU Emacs, the Swiss army knife of text
> editors" <bug-gnu-emacs <at> gnu.org> writes:
>
> > Okay, I think that one was my bad, as I was using the unmaintained melpa
> > version.
>
> Maybe someone could ask the MELPA maintainers to remove that outdated
> package?
>
>
>
>
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Sun, 09 Feb 2025 15:07:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 76131 <at> debbugs.gnu.org (full text, mbox):
Ship Mints <shipmints <at> gmail.com> writes:
> I had the stale version installed from MELPA myself so I installed the ELPA
> version and it looks like package reported the incorrect path name but
> under the covers did the right thing.
The vlf package is still on MELPA. I'm asking if it should be removed.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Sun, 09 Feb 2025 17:07:01 GMT)
Full text and
rfc822 format available.
Message #29 received at 76131 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefankangas <at> gmail.com> writes:
> fap via "Bug reports for GNU Emacs, the Swiss army knife of text
> editors" <bug-gnu-emacs <at> gnu.org> writes:
>
>> Okay, I think that one was my bad, as I was using the unmaintained melpa
>> version.
>
> Maybe someone could ask the MELPA maintainers to remove that outdated
> package?
I've removed it from Melpa and updated the Emacsmirror to get it from
elpa.git.
Stefan K, please change this in elpa.git/elpa-packages:
- (vlf :url "https://github.com/m00natic/vlfi") ;FIXME:Dead?
+ (vlf :url nil) ;"https://github.com/m00natic/vlfi"
After six years it's probably safe to assume this repository is not
suddenly coming back to live any time soon.
Andrey, please consider archiving your repository, but first add a brief
statement at the beginning of the README.org, stating that this is now
maintained inside GNU ELPA.
Cheers,
Jonas
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Sun, 09 Feb 2025 17:36:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 76131 <at> debbugs.gnu.org (full text, mbox):
Jonas Bernoulli <jonas <at> bernoul.li> writes:
> Stefan Kangas <stefankangas <at> gmail.com> writes:
>
>> fap via "Bug reports for GNU Emacs, the Swiss army knife of text
>> editors" <bug-gnu-emacs <at> gnu.org> writes:
>>
>>> Okay, I think that one was my bad, as I was using the unmaintained melpa
>>> version.
>>
>> Maybe someone could ask the MELPA maintainers to remove that outdated
>> package?
>
> I've removed it from Melpa and updated the Emacsmirror to get it from
> elpa.git.
Thanks!
> Stefan K, please change this in elpa.git/elpa-packages:
>
> - (vlf :url "https://github.com/m00natic/vlfi") ;FIXME:Dead?
> + (vlf :url nil) ;"https://github.com/m00natic/vlfi"
Done.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#76131
; Package
emacs
.
(Mon, 10 Feb 2025 12:31:01 GMT)
Full text and
rfc822 format available.
Message #35 received at 76131 <at> debbugs.gnu.org (full text, mbox):
> From: Ship Mints <shipmints <at> gmail.com>
> Date: Sun, 9 Feb 2025 09:56:51 -0500
> Cc: fap <hello <at> fap.re>, Eli Zaretskii <eliz <at> gnu.org>, Jonas Bernoulli <jonas <at> bernoul.li>,
> 76131 <at> debbugs.gnu.org
>
> I had the stale version installed from MELPA myself so I installed the ELPA version and it looks like package
> reported the incorrect path name but under the covers did the right thing.
>
> "Package vlf is installed.
>
> Status: Installed in 'vlf-20191126.2250/'. <<<---- incorrect path: it was put in vlf-1.7.2/
> Version: 20191126.2250
> Commit: cc02f2533782d6b9b628cec7e2dcf25b2d05a27c
> Summary: View Large Files.
> Website: https://github.com/m00natic/vlfi
> Keywords: large files utilities
> Other versions: 1.7.2 (installed), 20191126.2250 (melpa), 1.7.2 (gnu)."
So can we close this bug now, or is there anything left to do?
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Sat, 22 Feb 2025 09:33:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
fap <hello <at> fap.re>
:
bug acknowledged by developer.
(Sat, 22 Feb 2025 09:33:03 GMT)
Full text and
rfc822 format available.
Message #40 received at 76131-done <at> debbugs.gnu.org (full text, mbox):
> Cc: jonas <at> bernoul.li, stefankangas <at> gmail.com, hello <at> fap.re,
> 76131 <at> debbugs.gnu.org
> Date: Mon, 10 Feb 2025 14:30:16 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
>
> > From: Ship Mints <shipmints <at> gmail.com>
> > Date: Sun, 9 Feb 2025 09:56:51 -0500
> > Cc: fap <hello <at> fap.re>, Eli Zaretskii <eliz <at> gnu.org>, Jonas Bernoulli <jonas <at> bernoul.li>,
> > 76131 <at> debbugs.gnu.org
> >
> > I had the stale version installed from MELPA myself so I installed the ELPA version and it looks like package
> > reported the incorrect path name but under the covers did the right thing.
> >
> > "Package vlf is installed.
> >
> > Status: Installed in 'vlf-20191126.2250/'. <<<---- incorrect path: it was put in vlf-1.7.2/
> > Version: 20191126.2250
> > Commit: cc02f2533782d6b9b628cec7e2dcf25b2d05a27c
> > Summary: View Large Files.
> > Website: https://github.com/m00natic/vlfi
> > Keywords: large files utilities
> > Other versions: 1.7.2 (installed), 20191126.2250 (melpa), 1.7.2 (gnu)."
>
> So can we close this bug now, or is there anything left to do?
No further comments, so I'm now closing this bug.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 22 Mar 2025 11:24:08 GMT)
Full text and
rfc822 format available.
This bug report was last modified 147 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.