From: storm@cua.dk (Kim F. Storm)
Cc: monnier+gnu/emacs@RUM.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: table.el 1.6.1
Date: 21 Mar 2002 09:45:38 +0100 [thread overview]
Message-ID: <5xr8megvgt.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <20020320.213722.110254553.Takaaki.Ota@am.sony.com>
Tak Ota <Takaaki.Ota@am.sony.com> writes:
> Wed, 20 Mar 2002 20:38:56 -0500: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu> wrote:
>
> > > So far I find one problem. Somehow when point goes inside a table
> > > cell the table menu does not appear in the menu bar. For this part
> > > the same code works fine under emacs-21.1.90 although command remap is
> > > missing. Has the menu mechanism in keymap changed under 21.3?
> >
> > I seem to remember that something was changed in that area as part
> > of the command remap thingy. It was claimed at the time that
> > position-dependent menubar entries (i.e. menu-bar bindings in
> > `keymap' and `local-map' text properties) did not work and
> > should be taken out.
>
> Try run the table.el under 21.1.90. When the point enters a cell the
> table menu does appear, and disappears when point goes out.
>
> > Are you saying that they did work ?
>
> Yes, the position-dependent menubar entry does work under 21.1.90,
> however does not work under 21.2.50 and 20.7.
Following up on my previous note:
It just occurred to me that turning on column-number-mode actually
does force a mode-line (and menu-bar) update after every command,
so maybe the table.el code doesn't do anything special to make
this happen; if you have column-number-mode turn on, it will work.
Tak, do you have c-n-m turned on?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-21 8:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 5:22 table.el 1.6.1 Tak Ota
2002-03-21 1:38 ` Stefan Monnier
2002-03-21 5:37 ` Tak Ota
2002-03-21 8:41 ` Kim F. Storm
2002-03-21 21:43 ` Kim F. Storm
2002-03-21 22:20 ` Tak Ota
2002-03-21 8:45 ` Kim F. Storm [this message]
2002-03-21 9:13 ` Tak Ota
2002-03-22 12:26 ` Richard Stallman
2002-03-22 15:01 ` Kim F. Storm
2002-03-22 15:12 ` Kim F. Storm
2002-03-22 15:48 ` Tak Ota
2002-03-22 16:13 ` Kim F. Storm
2002-03-22 17:00 ` Stefan Monnier
2002-03-22 18:15 ` Tak Ota
2002-03-23 16:14 ` Richard Stallman
2002-03-23 17:11 ` Kim F. Storm
2002-03-25 0:19 ` Richard Stallman
2002-03-25 21:59 ` Stefan Monnier
2002-03-25 22:26 ` Kim F. Storm
2002-03-28 20:48 ` Richard Stallman
2002-03-28 23:21 ` Kim F. Storm
2002-03-30 3:43 ` Richard Stallman
2002-03-31 20:40 ` Kim F. Storm
2002-03-31 21:56 ` Miles Bader
2002-03-22 6:01 ` table.el 1.6.3 Tak Ota
-- strict thread matches above, loose matches on Subject: below --
2002-03-20 21:30 table.el 1.6.1 Tak Ota
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=5xr8megvgt.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@RUM.cs.yale.edu \
/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).