From: "Drew Adams" <drew.adams@oracle.com>
To: "'tiefeng wu'" <icebergwtf@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: bind a hotkey to toggle variable
Date: Sun, 12 Jul 2009 23:50:22 -0700 [thread overview]
Message-ID: <00EDDADB1DF84973BE9BE9A6FC7D31A2@us.oracle.com> (raw)
In-Reply-To: <4314c1f70907122012j638e717cw984a0defd893455f@mail.gmail.com>
> > See the Elisp manual, node `Defining Commands'.
>
> thanks Adams, I'll read the manual carefully.
>
> btw, I'm using your elisp library and having my pop-up-frames variable
> default setting to t, Recently I'm trying IDE-like 'nav' mode from
> google code, and the setting of pop-up-frames starts conflict with
> nav, because for 'nav' it's better open files in same frame. So this
> question occured.
I'm not familiar with `nav' mode, and I don't know which of my libraries you
mean. But I'm not surprised that some other code (e.g. `nav') has some problems
with non-nil `pop-up-frames'.
Unfortunately, it's all too common that code, including some vanilla Emacs
distribution code, does not play well with non-nil `pop-up-frames'. Developers
who use nil `pop-up-frames' seem too often not to test their code also with the
value non-nil. (And they especially seem not to test it using a standalone
minibuffer frame.)
To be able to use non-nil `pop-up-frames', users really have to jump through
quite a few hoops, and few actually bother. One-On-One Emacs helps make life
with non-nil `pop-up-frames' easier, but you can still run into other code that
can't handle it.
Frankly, I'm always surprised that, 20-30 years after the introduction of
graphic displays and window managers, most people still use Emacs windows, not
frames, for most buffers. That Emacs doesn't play very well with non-nil
`pop-up-frames' could explain that in part, but why people still use Emacs
windows so much is generally a mystery to me.
I've preferred frames over Emacs windows ever since frames became available, but
we're a tiny minority in that camp. And my impression is that each of us tames
the attendant problems slightly differently.
Wrt working with `nav': I know nothing about it, but perhaps there is an easy
way (e.g., using a mode hook or `same-window-*'), to use nil `pop-up-frames' for
`nav' buffers only. That should be doable, I would think.
BTW, googling a bit for `emacs nav' gives me the impression that `nav' is used
in particular with a terminal, not necessarily with a window manager. In that
case (i.e., if you are not using a window manager), is there much value in
having non-nil `pop-up-frames'? Dunno.
next prev parent reply other threads:[~2009-07-13 6:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 16:28 bind a hotkey to toggle variable tiefeng wu
2009-07-12 18:27 ` Drew Adams
[not found] ` <4314c1f70907121936r6a74003aya2bb42b1bfb56d35@mail.gmail.com>
2009-07-13 3:12 ` tiefeng wu
2009-07-13 6:50 ` Drew Adams [this message]
2009-07-13 8:24 ` Peter Dyballa
2009-07-13 8:47 ` Drew Adams
2009-07-13 9:15 ` Peter Dyballa
2009-07-13 15:02 ` Drew Adams
2009-07-13 9:10 ` tiefeng wu
[not found] ` <mailman.2406.1247467827.2239.help-gnu-emacs@gnu.org>
2009-07-13 10:10 ` Miles Bader
2009-07-13 11:06 ` Peter Dyballa
2009-07-13 15:02 ` Drew Adams
[not found] ` <mailman.2432.1247497373.2239.help-gnu-emacs@gnu.org>
2009-07-14 1:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00EDDADB1DF84973BE9BE9A6FC7D31A2@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=icebergwtf@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.