all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Evgeny Roubinchtein <zhenya@freeshell.org>
Subject: Re: Emacs configuration
Date: Tue, 01 Oct 2002 06:04:01 GMT	[thread overview]
Message-ID: <877kh2d7an.fsf@freeshell.org> (raw)
In-Reply-To: mailman.1033377809.21117.help-gnu-emacs@gnu.org

>>>>> "AC" == arthur chereau <arthur.chereau> writes:

    AC> - Is it possible to change the menu ordering, for instance
    AC>   moving Buffers before Files ?

You could do that by surgery on the keymap which is the value of the
[menu-bar] entry in the global-map, but that's _really_ ugly,
something like:

(let ((lst (lookup-key global-map [menu-bar]))
            (prev nil)
            buf-menu
            current)
        (while lst
          (setq current (car lst))
          (when (and (listp current) (eq (car current) 'buffer))
            (setcdr prev (cdr lst))
            (setq buf-menu current))
          (setq prev lst
                  lst (cdr lst)))
        (define-key global-map [menu-bar buffer] buf-menu))

Can anyone think of a less ugly alternative?

    AC>  Is there any means of having only one emacs process running
    AC>  for all the emacs windows? I mean, not like emacsclient or
    AC>  gnuserv, but when one calls emacs from the command line,
    AC>  having emacs spawn a new window like C-x 5 2 but no new
    AC>  process (to speed up the start).

You would need the emacs process that's already running to run a
server of _some_ kind: otherwise, how would it know to open a new
window?  To the best of my knowledge, the only standard servers that
come with Emacs are emacsserv and gnuserv.  You could conceivably hack
emacs to react to SIGUSR1, or somesuch, by opening a new window.  I
have no idea how hard/easy it would be.

  parent reply	other threads:[~2002-10-01  6:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1033377809.21117.help-gnu-emacs@gnu.org>
2002-09-30 17:01 ` Emacs configuration Jesper Harder
2002-09-30 17:02 ` Kevin Rodgers
2002-10-01  6:04 ` Evgeny Roubinchtein [this message]
2002-10-01 14:57 ` Stefan Monnier <foo@acm.com>
2021-09-30 15:13 emacs configuration Jude DaShiell
2021-09-30 15:56 ` tomas
2021-09-30 16:05   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-30 15:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-30 17:32   ` 2QdxY4RzWzUUiLuE
2021-09-30 21:49   ` Jean Louis
2021-09-30 22:11     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-01 20:34       ` Jean Louis
2021-09-30 16:03 ` 2QdxY4RzWzUUiLuE
2021-09-30 16:38 ` John W Higgins
     [not found] <mailman.1033485728.6848.help-gnu-emacs@gnu.org>
2002-10-01 20:45 ` Emacs configuration Jesper Harder
  -- strict thread matches above, loose matches on Subject: below --
2002-10-01 15:21 arthur.chereau
     [not found] <mailman.1033477527.28155.help-gnu-emacs@gnu.org>
2002-10-01 14:09 ` Jesper Harder
2002-10-01 13:04 arthur.chereau
2002-09-30  9:22 arthur.chereau

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=877kh2d7an.fsf@freeshell.org \
    --to=zhenya@freeshell.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 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.