From: Harry Putnam <hgp@sbcglobal.net>
Subject: Re: Multibyte chars
Date: Fri, 09 May 2003 04:33:35 GMT [thread overview]
Message-ID: <m21xz8rb70.fsf@sbcglobal.net> (raw)
In-Reply-To: ur879sxhz.fsf@ID-87814.user.dfncis.de
Oliver Scholz <alkibiades@gmx.de> writes:
[...]
> do you have `(standard-display-european t)' somewhere in you .emacs?
[...]
Yup.. an overlooked holdover from long ago lurking in site-start.el
Not exactly as you guessed:
(standard-display-european 1)
1 instead of t but I think it does the same eh?
> But I think that all this will just work, if you find out what causes
> your Emacs to use a unibyte buffer.
Removing that line caused the buffer to appear normal now ... thanks
prev parent reply other threads:[~2003-05-09 4:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5300.1051558114.21513.help-gnu-emacs@gnu.org>
2003-04-29 9:58 ` multiple inserts within skeletons Oliver Scholz
2003-04-29 10:52 ` Oliver Lohmann
2003-04-29 14:51 ` Harry Putnam
2003-04-29 16:22 ` Oliver Scholz
2003-04-29 23:13 ` Harry Putnam
2003-04-30 9:23 ` Oliver Scholz
2003-05-07 20:24 ` Multibyte chars [was Re: multiple inserts within skeletons] Harry Putnam
2003-05-08 7:34 ` Multibyte chars Oliver Scholz
2003-05-09 4:33 ` Harry Putnam [this message]
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=m21xz8rb70.fsf@sbcglobal.net \
--to=hgp@sbcglobal.net \
/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).