From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Feature request: share search ring amongst emacses
Date: Thu, 20 Jun 2002 08:33:53 -0600 (MDT) [thread overview]
Message-ID: <200206201433.g5KEXrq18577@aztec.santafe.edu> (raw)
In-Reply-To: <874rg0h5sr.fsf@jidanni.org> (message from Dan Jacobson on 19 Jun 2002 01:09:56 +0800)
Why are you using two separate Emacses?
If there is a good reason and that is really necessary for you,
maybe we can do something to correct the underlying problem
so you can use just one.
next parent reply other threads:[~2002-06-20 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874rg0h5sr.fsf@jidanni.org>
2002-06-20 14:33 ` Richard Stallman [this message]
2002-06-20 15:01 ` Feature request: share search ring amongst emacses Simon Josefsson
2002-06-21 14:14 ` Mario Lang
2002-06-21 16:04 ` Andreas Schwab
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=200206201433.g5KEXrq18577@aztec.santafe.edu \
--to=rms@gnu.org \
--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).