unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Geoffrey Alan Washburn <geoffw@cis.upenn.edu>
To: emacs-devel@gnu.org
Subject: Re: modify-syntax-entry and UTF8?
Date: Fri, 25 May 2007 14:20:53 -0400	[thread overview]
Message-ID: <46572905.1070607@cis.upenn.edu> (raw)
In-Reply-To: <87sl9kaixs.fsf@catnip.gol.com>

Miles Bader wrote:
> Geoffrey Alan Washburn <geoffw@cis.upenn.edu> writes:
>> Still broken, at least in the latest CVS version of the emacs-unicode-2 
>> branch.  Is there another branch that I should be using (or alternately
>> have its changes merged into emacs-unicode-2)?
> 
> I'm using my own branch, derived from the CVS emacs-unicode-2 branch
> (I don't think my personal changes are relevant to this area).
> 
> So how come it works for me but not for you?
> 
> I use the following command to invoke Emacs (where /tmp/m is your
> message):
> 
>    env - TERM=xterm emacs -nw -Q /tmp/m
> 
> [The non-ascii chars are displayed as question-marks because Emacs
> doesn't know what character set the terminal supports, but they still
> match correctly.]

Okay, one difference was that I wasn't running emacs in terminal mode. 
However, I tried your example which worked and then reverted to my 
normal configuration and now that seems to be working too.  So this 
really got me worried that I was just doing something really silly. 
However, if I start a fresh buffer and then use X11 "cut and paste" to 
copy ⟨   ⟩ into the buffer (instead of reading it from a file) it 
doesn't work.  If I am editing a file that I've opened that already 
contains ⟨   ⟩ "cut and paste" a second pair, those match correctly as 
well.  Alternately, if I first "cut and paste" and then use insert-file, 
matching behaves incorrectly.  So I'm sure whether this is a 
configuration error on my part, or some bugginess regarding interaction 
with the X server.  I was pretty sure that I emacs configured to use the 
correct encoding to start with

set-language-environment "utf-8")
(set-keyboard-coding-system 'utf-8)
(set-terminal-coding-system 'utf-8)
(prefer-coding-system 'utf-8)

I just checked and when opening a file with the pair of delimiters, 
describe-coding-system says

Coding system for saving this buffer:
   U -- utf-8-unix (alias: mule-utf-8-unix)

Default coding system (for new files):
   U -- utf-8 (alias: mule-utf-8)

Coding system for keyboard input:
   U -- utf-8 (alias: mule-utf-8)

Coding system for terminal output:
   U -- utf-8 (alias: mule-utf-8)

Coding system for inter-client cut and paste:
   x -- compound-text-with-extensions (alias: x-ctext-with-extensions 
ctext-with-extensions)

Defaults for subprocess I/O:
   decoding: U -- utf-8-unix (alias: mule-utf-8-unix)

   encoding: U -- utf-8-unix (alias: mule-utf-8-unix)

whereas when I open a fresh buffer I get

Coding system for saving this buffer:
   Not set locally, use the default.
Default coding system (for new files):
   U -- utf-8 (alias: mule-utf-8)

Coding system for keyboard input:
   U -- utf-8 (alias: mule-utf-8)

Coding system for terminal output:
   U -- utf-8 (alias: mule-utf-8)

Coding system for inter-client cut and paste:
   x -- compound-text-with-extensions (alias: x-ctext-with-extensions 
ctext-with-extensions)

Defaults for subprocess I/O:
   decoding: U -- utf-8-unix (alias: mule-utf-8-unix)

   encoding: U -- utf-8-unix (alias: mule-utf-8-unix)


If I change my .emacs so that it has

(prefer-coding-system 'utf-8-unix)

describe-coding-system reports both cases as identical to the first I 
quoted above.  However, the behavior for working with a fresh buffer 
versus and opened file remains the same.

  reply	other threads:[~2007-05-25 18:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 17:24 modify-syntax-entry and UTF8? Geoffrey Alan Washburn
2007-05-21 23:06 ` James Cloos
2007-05-22  8:47   ` Geoffrey Alan Washburn
2007-05-22 13:25     ` James Cloos
2007-05-23 15:09       ` Geoffrey Alan Washburn
2007-05-23 16:56         ` Stefan Monnier
2007-05-25 13:48           ` Geoffrey Alan Washburn
2007-05-25 14:23             ` Miles Bader
2007-05-25 14:26               ` Geoffrey Alan Washburn
2007-05-25 14:54                 ` Geoffrey Alan Washburn
2007-05-25 17:53                   ` Miles Bader
2007-05-25 18:20                     ` Geoffrey Alan Washburn [this message]
2007-05-25 22:06                 ` James Cloos
2007-05-28 16:04                   ` Geoffrey Alan Washburn
2007-05-29 12:43                     ` highlights of parentheses in lisp-interaction-mode (was: Re: modify-syntax-entry and UTF8?) James Cloos
2007-05-29 13:27                       ` highlights of parentheses in lisp-interaction-mode martin rudalics
2007-05-29 16:34                         ` James Cloos
2007-06-04  0:17                       ` highlights of parentheses in lisp-interaction-mode (was: Re: modify-syntax-entry and UTF8?) Richard Stallman
2007-05-22  9:48 ` modify-syntax-entry and UTF8? 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=46572905.1070607@cis.upenn.edu \
    --to=geoffw@cis.upenn.edu \
    --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).