From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Frank Roland <frokrecik@gmail.com>
Cc: 24920@debbugs.gnu.org
Subject: bug#24920: 24.5; Error on customize-update-all
Date: Thu, 10 Nov 2016 14:29:00 -0500 [thread overview]
Message-ID: <CAM-tV--gNYBHW8vWxBbz-q6NqVmhr9BbbRJiyzkdGmcL-uPHYw@mail.gmail.com> (raw)
In-Reply-To: <CAF3WaZvr3Qfvii455wW9uK3yspMExc2L65_PR2zT-tjsK4uHug@mail.gmail.com>
On Thu, Nov 10, 2016 at 11:52 AM, Frank Roland <frokrecik@gmail.com> wrote:
> I was not realy doing anything. After some tome a hook got triggered and
> caused an error, see backtrace:
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> file-name-directory(nil)
> (expand-file-name "../var/auctex" (file-name-directory load-file-name))
> eval((expand-file-name "../var/auctex" (file-name-directory load-file-name)))
> #[(symbol) "had to delete that binary data strings..." [symbol cval
> customized-value saved-value standard-value default-boundp eval
> default-value put custom-quote] 7](TeX-auto-global)
> mapatoms(#[(symbol) " Again, binary deleted" [symbol cval
> customized-value saved-value standard-value default-boundp eval
> default-value put custom-quote] 7])
> customize-update-all-vars()
> customize-update-all()
> apply(customize-update-all nil)
> byte-code("r\301 \302H \303H\"\210)\301\207" [timer apply 5 6] 4)
> timer-event-handler([t 0 60 0 t customize-update-all nil idle 0])
>
>
I guess this is either a bug in cus-edit+ (wrongly assuming any of
customized-value, saved-value, standard-value can be `eval'ed in any
buffer), or it's a bug in Auctex (for putting a customized-value,
saved-value, or standard-value that can't be `eval'ed in any buffer).
Does M-x customize-option TeX-auto-global RET give a similar error?
next prev parent reply other threads:[~2016-11-10 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 16:52 bug#24920: 24.5; Error on customize-update-all Frank Roland
2016-11-10 19:29 ` Noam Postavsky [this message]
2016-11-10 22:59 ` Drew Adams
2016-11-10 23:59 ` npostavs
2021-09-03 9:03 ` Lars Ingebrigtsen
2022-05-02 10:12 ` Lars Ingebrigtsen
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=CAM-tV--gNYBHW8vWxBbz-q6NqVmhr9BbbRJiyzkdGmcL-uPHYw@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=24920@debbugs.gnu.org \
--cc=frokrecik@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).