From: ken <gebser@speakeasy.net>
To: help-gnu-emacs@gnu.org
Subject: Re: replacing characters and whacky trans-buffer conversion
Date: Thu, 08 Mar 2007 06:55:57 -0500 [thread overview]
Message-ID: <45EFF9CD.5030309@speakeasy.net> (raw)
In-Reply-To: <45EFE810.8010009@speakeasy.net>
On 03/08/2007 05:40 AM somebody named ken wrote:
> On 03/08/2007 02:50 AM somebody named Stefan Monnier wrote:
>>> The first buffer is a *scratch* buffer, the modeline starts "--:". The
>>> second contains the *.el file mentioned in the original post; its
>>> modeline begins "-:".
>> For some reason this second buffer is in unibyte mode.
>> That's the source of your problem. Tell us how you created that buffer.
>
> C-x C-f
>
> ....
I should add that this is how I create most all files in emacs.
Occasionally I'll use vi(m) to create or edit a file and subsequently
edit it using emacs. Less occasionally I'll use "cat > filename" to
create a file, or "[some (series of) command(s)] > filename" and then
pull it into emacs. And, as mentioned earlier, sometimes I'll open a
file (C-x C-f) and yank the clipboard contents into it. It seems you're
implying that different means of creating a file will force emacs' use
of different character encodings, yes? (Actually, I've encountered many
times that emacs, after C-x C-s, tells me to select some other encoding
system... which I almost never want to do.)
tnx
--
"Genius might be described as a supreme capacity for getting its
possessors into trouble of all kinds."
-- Samuel Butler
next prev parent reply other threads:[~2007-03-08 11:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 15:15 replacing characters and whacky trans-buffer conversion ken
2007-03-06 16:28 ` Peter Dyballa
2007-03-07 7:38 ` Matthew Flaschen
2007-03-07 9:59 ` Peter Dyballa
2007-03-08 12:16 ` ken
2007-03-08 16:31 ` Peter Dyballa
2007-03-08 20:43 ` ken
2007-03-08 23:14 ` Peter Dyballa
[not found] ` <mailman.688.1173395790.7795.help-gnu-emacs@gnu.org>
2007-03-09 14:28 ` Oliver Scholz
2007-03-07 20:48 ` ken
2007-03-07 21:03 ` ken
2007-03-07 21:30 ` Peter Dyballa
2007-03-08 1:11 ` ken
[not found] ` <mailman.627.1173316331.7795.help-gnu-emacs@gnu.org>
2007-03-08 7:50 ` Stefan Monnier
2007-03-08 10:40 ` ken
2007-03-08 11:55 ` ken [this message]
[not found] ` <mailman.648.1173350436.7795.help-gnu-emacs@gnu.org>
2007-03-09 1:51 ` Stefan Monnier
2007-03-09 10:15 ` ken
2007-03-09 13:14 ` Peter Dyballa
2007-03-09 15:54 ` ken
2007-03-09 16:13 ` Peter Dyballa
2007-03-09 18:41 ` Reiner Steib
2007-03-10 18:29 ` ken
2007-03-10 18:57 ` Reiner Steib
2007-03-10 19:00 ` Peter Dyballa
2007-03-10 19:12 ` Eli Zaretskii
2007-03-09 10:21 ` ken
2007-03-09 13:02 ` Peter Dyballa
[not found] ` <mailman.699.1173435731.7795.help-gnu-emacs@gnu.org>
2007-03-09 20:20 ` Stefan Monnier
2007-03-10 18:32 ` ken
[not found] ` <mailman.698.1173435330.7795.help-gnu-emacs@gnu.org>
2007-03-09 20:34 ` Stefan Monnier
2007-03-09 22:00 ` Oliver Scholz
[not found] <mailman.528.1173194164.7795.help-gnu-emacs@gnu.org>
2007-03-06 16:41 ` Oliver Scholz
2007-03-06 17:52 ` 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=45EFF9CD.5030309@speakeasy.net \
--to=gebser@speakeasy.net \
--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).