From: Kenichi Handa <handa@etl.go.jp>
Cc: emacs-devel@gnu.org
Subject: Re: Attempt to modify read-only value
Date: Tue, 23 Apr 2002 17:12:39 +0900 (JST) [thread overview]
Message-ID: <200204230812.RAA16183@etlken.m17n.org> (raw)
In-Reply-To: message from Juanma Barranquero on Tue, 23 Apr 2002 09:50:10 +0200
Juanma Barranquero <lektu@terra.es> writes:
> After this:
> 2002-04-23 Miles Bader <miles@gnu.org>
> * menu-bar.el (menu-bar-update-buffers): Add `Select Named Buffer'.
> Add separator line before commands
> Remove old crufty code that tried to line things up by adding
> spaces to entries (it doesn't work).
> Move `Frames' submenu after the normal buffers, and add a
> separator line before it.
> (menu-bar-buffers-menu-list-buffers-entry): Variable removed.
> I'm getting "attempt to modify read-only value" while bootstraping.
Me too. This is because, in keyboard.c, we do this:
if (NILP (cachelist))
{
/* We have to create a cachelist. */
CHECK_IMPURE (start); <-- this causes the error
XSETCDR (start, Fcons (Fcons (Qnil, Qnil), XCDR (start)));
Changing this part (line 1363 of menu-bar.el):
'((command-separator "--")
(select-named-buffer
menu-item
"Select Named Buffer..."
switch-to-buffer
:help "Prompt for a buffer name, and select that buffer in the current window")
(list-all-buffers
menu-item
"List All Buffers"
list-buffers
:help "Pop up a window listing all emacs buffers"))))
to something like:
`((command-separator "--")
,(list 'select-named-buffer
'menu-item
"Select Named Buffer..."
'switch-to-buffer
...)
,(list 'list-all-buffers
'menu-item
"List All Buffers"
'list-buffers
...))
fixes this problem. But, this workaround is very weird.
There should be a better solution.
---
Ken'ichi HANDA
handa@etl.go.jp
next reply other threads:[~2002-04-23 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 8:12 Kenichi Handa [this message]
2002-04-23 8:48 ` Attempt to modify read-only value Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2002-04-23 11:20 Kenichi Handa
2002-04-23 7:50 Juanma Barranquero
2002-04-23 8:43 ` Miles Bader
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=200204230812.RAA16183@etlken.m17n.org \
--to=handa@etl.go.jp \
--cc=emacs-devel@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).