From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: buffer-swap-text and multibyteness
Date: Tue, 03 Feb 2009 16:59:36 +0900 [thread overview]
Message-ID: <E1LUGC0-0002Zy-Tv@etlken> (raw)
In-Reply-To: <jwvpri14l9n.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 01 Feb 2009 21:39:05 -0500)
In article <jwvpri14l9n.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > I think rmail-buffer and rmail-view-buffer should be set
> > consistently to the unibyte buffer containing RMAIL file and
> > to the multibyte buffer showing one message to a user.
> > And, most of the interactive functions should just do
> > something like this:
> > (set-buffer rmail-buffer)
> > ...
> > (switch-to-buffer rmail-view-buffer)
> > Is the conbination of set-buffer and switch-to-buffer
> > heavier than two buffer-swap-text?
> Yes. we agree (except that switch-to-buffer is a function I would
> prefer to see disapppear, so better use something else like
> pop-to-buffer or just set-buffer).
Is above "Yes" also to this question?
> > Is the conbination of set-buffer and switch-to-buffer
> > heavier than two buffer-swap-text?
By the way,
> Also, I'd prefer to use `rmail-buffer' for the multibyte buffer that's
> displayed, and rmail-data-buffer for the raw unibyte mbox.
I don't have strong preference for those variable names as
far as their setting doesn't change by swapping.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-02-03 7:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 14:52 buffer-swap-text and multibyteness Eli Zaretskii
2009-01-31 17:12 ` Stefan Monnier
2009-01-31 19:03 ` Eli Zaretskii
2009-01-31 19:43 ` Stefan Monnier
2009-01-31 20:05 ` Eli Zaretskii
2009-01-31 21:28 ` Stefan Monnier
2009-01-31 22:02 ` Eli Zaretskii
2009-02-01 1:43 ` Stefan Monnier
2009-02-01 4:13 ` Eli Zaretskii
2009-02-01 21:43 ` Stefan Monnier
[not found] ` <E1LTl7l-0005Dm-8W@fencepost.gnu.org>
2009-02-02 1:26 ` Stefan Monnier
2009-02-02 2:37 ` Kenichi Handa
2009-02-02 2:48 ` Kenichi Handa
2009-02-05 4:26 ` Stefan Monnier
2009-02-07 12:58 ` Eli Zaretskii
2009-02-09 11:31 ` Kenichi Handa
2009-02-09 14:11 ` Stefan Monnier
2009-02-09 20:26 ` Eli Zaretskii
2009-02-10 2:03 ` Stefan Monnier
2009-02-10 8:49 ` Eli Zaretskii
2009-02-10 21:57 ` Stefan Monnier
2009-02-11 4:01 ` Eli Zaretskii
2009-02-11 14:10 ` Stefan Monnier
2009-02-11 9:24 ` Kenichi Handa
[not found] ` <umycvs6a0.fsf@gnu.org>
2009-02-10 8:17 ` Kenichi Handa
2009-02-10 9:12 ` Eli Zaretskii
2009-02-10 11:52 ` Kenichi Handa
2009-02-21 15:12 ` Eli Zaretskii
2009-02-24 8:09 ` Kenichi Handa
2009-02-24 18:48 ` Eli Zaretskii
2009-02-25 1:15 ` Kenichi Handa
2009-02-25 4:11 ` Eli Zaretskii
2009-02-26 5:48 ` Kenichi Handa
2009-02-02 4:09 ` Eli Zaretskii
2009-02-01 22:49 ` Richard M Stallman
2009-02-02 2:14 ` Kenichi Handa
2009-02-02 2:39 ` Stefan Monnier
2009-02-03 7:59 ` Kenichi Handa [this message]
2009-02-03 16:46 ` Stefan Monnier
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=E1LUGC0-0002Zy-Tv@etlken \
--to=handa@m17n.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).