all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Harald Maier <harald@maierh.de>
Cc: 2375@emacsbugs.donarmstrong.com
Subject: bug#2375: 23.0.90; ^ in gnus summary buffer does not work in the nextstep build
Date: Tue, 24 Feb 2009 14:09:02 +0900	[thread overview]
Message-ID: <wl7i3g8lqp.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <m2tz6ko2e1.fsf@ate.maierh>

>>>>> On Tue, 24 Feb 2009 06:00:22 +0100, Harald Maier <harald@maierh.de> said:

>>>> What do you think about the dead-key behavior in the Carbon port
>>>> (Emacs 22)?  If it is reasonable enough, maybe the Cocoa/GNUstep
>>>> port can adopt its strategy.
>> 
>>> That works but I don't like it. My preference is as in the X11
>>> build.
>> 
>> Could you explain more in detail how they are different and why you
>> don't like it?  Note that some distributions (such as Carbon Emacs
>> Package or Aquamacs Emacs) based on the Carbon port applies some
>> patch with respect to text input, and their behavior is not
>> strictly the same as the Carbon port I'm talking about.

> It really inserts a caret character into the gnus summary buffer as
> you can see in the attached image. That looks very strange.

That's the point in the implementation: i.e., it gives a visual
feedback that indicates dead-key is being processed even in the
read-only buffer using an overlay string.  Such kind of feedback can
also be seen in other Mac applications (modulo colors/underline, which
is customizable in the Carbon port) and even in X11 apps with XIM.

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp






  reply	other threads:[~2009-02-24  5:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 18:27 bug#2375: 23.0.90; ^ in gnus summary buffer does not work in the nextstep build Harald Maier
2009-02-18 21:15 ` David Engster
2009-02-18 23:51   ` Stefan Monnier
2009-02-19 12:35     ` David Engster
2009-02-19 18:29       ` Stefan Monnier
2009-02-20  3:46         ` Harald Maier
2009-02-20 13:03         ` David Engster
2009-02-20 15:18           ` Stefan Monnier
2009-02-20 15:41             ` David Engster
2009-02-20 21:14               ` Stefan Monnier
2009-02-21  0:45                 ` David Engster
2009-02-21  4:56                 ` Harald Maier
2009-02-21  6:38                   ` YAMAMOTO Mitsuharu
2009-02-21  9:30                     ` Harald Maier
2009-02-22  1:39                       ` YAMAMOTO Mitsuharu
2009-02-24  5:00                         ` Harald Maier
2009-02-24  5:09                           ` YAMAMOTO Mitsuharu [this message]
2009-02-25 16:25                     ` Stefan Monnier
2009-02-26  0:04                       ` YAMAMOTO Mitsuharu
2009-02-26 15:21                         ` Stefan Monnier
2009-02-27  0:09                           ` YAMAMOTO Mitsuharu
2009-03-09 13:25                             ` Stefan Monnier
2009-03-10  0:05                               ` YAMAMOTO Mitsuharu
2009-03-10 17:18                                 ` Stefan Monnier
2015-02-13  7:18                           ` Lars Ingebrigtsen
2016-01-21 23:31                             ` Alan Third
2009-02-26 16:49                       ` David Engster

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wl7i3g8lqp.wl%mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=2375@emacsbugs.donarmstrong.com \
    --cc=harald@maierh.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.