unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Chris Patterson <chris@casapatterson.com>, nakkaya@gmail.com
Cc: GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: Re: emacs 23 term behaviour on OS X
Date: Mon, 11 Aug 2008 00:43:54 +0200	[thread overview]
Message-ID: <9A267F3E-9A69-44B4-A716-AE73A32446FA@Web.DE> (raw)
In-Reply-To: <m2zlnkk503.fsf@casapatterson.com>


Am 10.08.2008 um 22:08 schrieb Chris Patterson:

> Unfortunately it does the same thing in zsh, csh, etc and  
> regardless of
> starting with -Q. I'm thinking that this is something with the
> keybindings in Emacs.app because I have found that on my G4 Powerbook
> the Enter key does work though Return does not. I suppose it is  
> possible that
> the problem is related only to notebook keyboards and that could  
> explain the
> difficulty in reproducing.

I think I understand now: you both do not seem to use the big Return  
key on the far right but the little one close to the space bar. In  
the X client it acts like C-c (or C-@, ASCII NUL, when holding the FN  
key), in Emacs.app it's recognised as kp-enter (or C-p when holding  
the FN key). I've bound it to other-window ...

This could be another bug in Emacs.app – there are other keys it does  
not correctly understand. You should file a bug report!

>
> I are also having this issue with Tab and I've not found ^I to be a  
> suitable
> workaround here.

What are the symptoms? For me TAB fails in *shell* buffer to expand  
file names. I have reported this as a bug, the bug was closed as  
being fixed, but for me it's still there and I am missing a good  
proof ... There is also one with rather long lines as in 'ls -l  
`locate <some file name>`' or in 'set path=(...)' that I haven't  
reported yet since I also do not completely understand possible  
interaction with tcsh ... In GNU Emacs 22.2 and in 23.0.60 from  
January it works faultlessly.

--
Greetings

   Pete

Government is actually the worst failure of civilized man. There has  
never been a really good one, and even those that are most tolerable  
are arbitrary, cruel, grasping and unintelligent.
				– H. L. Mencken







  parent reply	other threads:[~2008-08-10 22:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 13:31 emacs 23 term behaviour on OS X nakkaya
2008-08-08 14:11 ` Peter Dyballa
     [not found] ` <mailman.16103.1218204687.18990.help-gnu-emacs@gnu.org>
2008-08-08 14:52   ` nakkaya
2008-08-08 16:32     ` Peter Dyballa
     [not found]     ` <mailman.16111.1218213140.18990.help-gnu-emacs@gnu.org>
2008-08-09  0:05       ` nakkaya
2008-08-10  1:23 ` Chris Patterson
2008-08-10 14:32   ` nakkaya
2008-08-10 17:53   ` Peter Dyballa
     [not found]     ` <m2zlnkk503.fsf@casapatterson.com>
2008-08-10 22:43       ` Peter Dyballa [this message]
     [not found]       ` <mailman.16318.1218408251.18990.help-gnu-emacs@gnu.org>
2008-08-11  1:58         ` nakkaya
2008-08-11  6:52           ` Peter Dyballa
     [not found]   ` <mailman.16291.1218390840.18990.help-gnu-emacs@gnu.org>
2008-08-10 20:39     ` nakkaya
2008-08-10 21:00       ` Peter Dyballa

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=9A267F3E-9A69-44B4-A716-AE73A32446FA@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=chris@casapatterson.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=nakkaya@gmail.com \
    /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).