From: Charlie Zender <zender@uci.edu>
To: help-gnu-emacs@gnu.org
Subject: has frames behavior changed?
Date: Fri, 06 Nov 2009 22:27:18 -0800 [thread overview]
Message-ID: <4AF51346.70804@uci.edu> (raw)
hi,
this message refers to using emacs 22.2.1, and
prior versions, on ubuntu linux.
once upon a time, until about 6 mos. - 1 yr. ago,
each emacs frame i opened behaved like a sub-process
of a single emacs process, e.g., if the same buffer
were displayed in multiple frames then editing that
buffer simultaneously updated all the frames.
now, though, when i open multiple frames in emacs,
the frames do not seem to know what's going on in the
other frames. i have not changed how i start emacs
at all. i like the old behavior better. anyone know
how to recover it?
gracias,
charlie
--
Charlie Zender, Department of Earth System Science
University of California, Irvine (949) 891-2429 :)
next reply other threads:[~2009-11-07 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 6:27 Charlie Zender [this message]
2009-11-07 13:08 ` has frames behavior changed? Alan Mackenzie
[not found] <mailman.10207.1257576016.2239.help-gnu-emacs@gnu.org>
2009-11-07 13:02 ` Pascal J. Bourguignon
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=4AF51346.70804@uci.edu \
--to=zender@uci.edu \
--cc=help-gnu-emacs@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.
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).