OSX: Keymaps get corrupted (?)

2005-09-29 Thread David Reitter
Over the recent two months or so, I've seen several reports of  
strangely corrupted keymaps in the Carbon port on OS X.
When that happens, no key input can be made (Error message: Wrong  
type argument: commandp).


It is not reproducible, but obviously occurs regularly for some users.

More detailed accounts here:

http://lists.sourceforge.jp/mailman/archives/macemacsjp-english/2005- 
July/000127.html


http://article.gmane.org/gmane.emacs.macintosh.osx/1346

possibly the same issue:

http://lists.gnu.org/archive/html/help-gnu-emacs/2005-09/msg00280.html

smime.p7s
Description: S/MIME cryptographic signature
___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


О чем говорит ваша фамилия?

2005-09-29 Thread Александр



Хотите прикаснуться к истории и узнать 
значение своей фамилии?
или, быть может, хотите преподнести неизбитый подарок
близкому или знакомому человеку? Ждем вас 
тут



http://www.terra.es/personal7/koleso16/history-fam/index.html

Серьезное исследование и отличный подарок


___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: new style Emacs compile v0.15

2005-09-29 Thread Richard M. Stallman
This is a reimplementation of error locating in Emacs `compile'.

Why reimplement it again?  The current implementation, done earlier
this year, seems to work well.  It had a few bugs at first, but they
have been fixed.


___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: new style Emacs compile v0.15

2005-09-29 Thread Nick Roberts
Richard M. Stallman writes:
  This is a reimplementation of error locating in Emacs `compile'.
  
  Why reimplement it again?  The current implementation, done earlier
  this year, seems to work well.  It had a few bugs at first, but they
  have been fixed.

That mail was dated: Tue, 16 Dec 2003 02:01:51 -.  There appears to have
been a backlog of large files which have just been delivered through the
archives.

Nick



___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: OSX: Keymaps get corrupted (?)

2005-09-29 Thread YAMAMOTO Mitsuharu
 On Thu, 29 Sep 2005 08:07:35 +0100, David Reitter [EMAIL PROTECTED] 
 said:

 Over the recent two months or so, I've seen several reports of
 strangely corrupted keymaps in the Carbon port on OS X.  When that
 happens, no key input can be made (Error message: Wrong type
 argument: commandp).

 It is not reproducible, but obviously occurs regularly for some
 users.

I've never seen this.  Maybe it's related to something I don't use
regularly.  

Let me confirm first.  Does it also occur on unmodified CVS version?

 YAMAMOTO Mitsuharu
[EMAIL PROTECTED]


___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


ps-print does not print and report correctly

2005-09-29 Thread Peter Dyballa

Hello!

Having an ISO Latin-15 encoded buffer that goes like this:

;;; -*- mode: Text; coding: iso-8859-15; -*-
;
;   Time-stamp: 2005-07-15 13:12:08 pete
;
;   Western European Glyphs with € (Latin 9, Latin 0)
;
;   oct   dec   hexUCS2UTF-8
;=
  = 240 = 160 = A0 = U+00A0 =C2 A0 : NO-BREAK SPACE
¡ = 241 = 161 = A1 = U+00A1 =C2 A1 : INVERTED EXCLAMATION MARK
¢ = 242 = 162 = A2 = U+00A2 =C2 A2 : CENT SIGN
£ = 243 = 163 = A3 = U+00A3 =C2 A3 : POUND SIGN
€ = 244 = 164 = A4 = U+20AC = E2 82 AC : EURO SIGN
¥ = 245 = 165 = A5 = U+00A5 =C2 A5 : YEN SIGN
	Š = 246 = 166 = A6 = U+0160 =C5 A0 : LATIN CAPITAL LETTER S WITH 
CARON

§ = 247 = 167 = A7 = U+00A7 =C2 A7 : SECTION SIGN

I get this *Warning* message when I choose 'PostScript Print Buffer' 
from the File menu:


These characters in the buffer can't be printed:
 €,  , ¡, ¢, £, €, ¥, Š, §, š, ©, ª, «, ¬, ­, and more...
Click them to jump to the buffer position,
or C-u C-x = will give information about them.

This is not true, because this is put into PS file:

LHL
/f0 F
(\240) S
/f0 F
( = 240 = 160 = A0 = U+00A0 =C2 A0 : NO-BREAK SPACE) S
LHL
/f0 F
(\241) S
/f0 F
( = 241 = 161 = A1 = U+00A1 =C2 A1 : INVERTED EXCLAMATION MARK) S
LHL
/f0 F
(\242) S
/f0 F
( = 242 = 162 = A2 = U+00A2 =C2 A2 : CENT SIGN) S
LHL
/f0 F
(\243) S
/f0 F
( = 243 = 163 = A3 = U+00A3 =C2 A3 : POUND SIGN) S
LHL
1 1 SB
/f0 F
( = 244 = 164 = A4 = U+20AC = E2 82 AC : EURO SIGN) S
LHL
/f0 F
(\245) S
/f0 F
( = 245 = 165 = A5 = U+00A5 =C2 A5 : YEN SIGN) S

As you can see only € is censored away, although it's hard to image 
that there is still some PostScript printer around that can't print €. 
Other cases of censorship are:


LHL
1 1 SB
/f0 F
	( = 246 = 166 = A6 = U+0160 =C5 A0 : LATIN CAPITAL LETTER S WITH 
CARON) S

LHL
1 1 SB
/f0 F
	( = 250 = 168 = A8 = U+0161 =C5 A1 : LATIN SMALL LETTER S WITH 
CARON) S

LHL
1 1 SB
/f0 F
	( = 264 = 180 = B4 = U+017D =C5 BD : LATIN CAPITAL LETTER Z WITH 
CARON) S

LHL
1 1 SB
/f0 F
	( = 270 = 184 = B8 = U+017E =C5 BE : LATIN SMALL LETTER Z WITH 
CARON) S

LHL
1 1 SB
/f0 F
( = 274 = 188 = BC = U+0152 =C5 92 : LATIN CAPITAL LIGATURE OE) S
LHL
1 1 SB
/f0 F
( = 275 = 189 = BD = U+0153 =C5 93 : LATIN SMALL LIGATURE OE) S
LHL
1 1 SB
/f0 F
	( = 276 = 190 = BE = U+0178 =C5 B8 : LATIN CAPITAL LETTER Y WITH 
DIAERESIS) S


It is censorship because it disables the user to further process the PS 
code to make it completely printable, for example by using a TrueType 
font with all the missing glyphs.




In GNU Emacs 22.0.50.1 (powerpc-apple-darwin7.9.0, X toolkit, Xaw3d 
scroll bars)

 of 2005-09-27 on Latsche.local
X server distributor `The XFree86 Project, Inc', version 11.0.4030
configured using `configure '--without-pop' '--with-xpm' '--with-jpeg' 
'--with-tiff' '--with-gif' '--with-png' 
'--enable-locallisppath=/Library/Application 
Support/Emacs/calendar:/Library/Application 
Support/Emacs/preview:/Library/Application 
Support/Emacs/auctex/images:/Library/Application 
Support/Emacs/auctex:/Library/Application Support/Emacs' 'CFLAGS=-ggdb 
-pipe -faltivec -maltivec -mcpu=740 -no-cpp-precomp 
-fomit-frame-pointer -foptimize-register-move -fcprop-registers 
-frename-registers -freorder-blocks -fpeephole -mpowerpc-gfxopt 
-mpowerpc-gpopt' 'CPPFLAGS=-I/usr/local/include -I/sw/include/libpng12 
-I/sw/lib/pango-ft219/include -I/sw/include/pango-1.0 
-I/sw/lib/freetype219/include -I/sw/include' 'LDFLAGS=-L/usr/X11R6/lib 
-L/usr/local/lib -L/sw/lib/ncurses -L/sw/lib/freetype219/lib 
-L/sw/lib/pango-ft219/lib -L/sw/lib''


Important settings:
  value of $LC_ALL: de_DE.UTF-8
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: de_DE.UTF-8
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: de_DE.UTF-8
  locale-coding-system: utf-8
  default-enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  desktop-save-mode: t
  display-time-mode: t
  mouse-sel-mode: t
  show-paren-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  tooltip-mode: t
  auto-compression-mode: t
  menu-bar-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t


--
Mit 

Re: OSX: Keymaps get corrupted (?)

2005-09-29 Thread David Reitter

On 29 Sep 2005, at 12:57, YAMAMOTO Mitsuharu wrote:

On Thu, 29 Sep 2005 08:07:35 +0100, David Reitter  
[EMAIL PROTECTED] said:






Over the recent two months or so, I've seen several reports of
strangely corrupted keymaps in the Carbon port on OS X.  When that
happens, no key input can be made (Error message: Wrong type
argument: commandp).





It is not reproducible, but obviously occurs regularly for some
users.



I've never seen this.  Maybe it's related to something I don't use
regularly.

Let me confirm first.  Does it also occur on unmodified CVS version?


I have only seen it happen once, and that was in Aquamacs without  
further changes.


We have reports of this happening in both Aquamacs and  
CarbonEmacsPackage, which do not share a whole lot of code.
I don't know about the status of this in CVS Emacs. I'm cc'ing two  
people who have reported this bug - maybe they can help out. 
 

smime.p7s
Description: S/MIME cryptographic signature
___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: Flyspell-mode breaks CUA mode

2005-09-29 Thread Kim F. Storm
LaserDoodads Info [EMAIL PROTECTED] writes:

 After starting Emacs with -Q I start flyspell-mode in the
 *scratch* buffer.  I then paste some text into the buffer and
 turn CUA mode on from the [options] menu.  If I try to select
 text using shifted arrow keys the selection is erratic.  That is,
 sometimes text will be selected and sometimes not.  Often text
 that is selected becomes suddenly unselected between keystrokes.

Others have reported problems with flyspell and transient-mark-mode,
and since CUA uses transient-mark-mode, I suppose this bug follows
from those problems (unless somebody can prove me wrong :-).

FTR, I'm _not_ looking into the flyspell pb.

-- 
Kim F. Storm [EMAIL PROTECTED] http://www.cua.dk



___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: new style Emacs compile v0.15

2005-09-29 Thread Richard M. Stallman
This is a reimplementation of error locating in Emacs `compile'.

Why reimplement it again?  The current implementation, done earlier
this year, seems to work well.  It had a few bugs at first, but they
have been fixed.


___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: Fonts: letter spacing bad (Carbon port)

2005-09-29 Thread YAMAMOTO Mitsuharu
 On Wed, 28 Sep 2005 11:56:07 +0100, David Reitter [EMAIL PROTECTED] 
 said:

 2. the problem is due to use of an deprecated API to show text.

Actually, David directly sent me the original report because it was
delayed due to the size limitation of the message to
emacs-pretest-bug.  Below is my answer at that time (a trivial typo is
corrected).

 On Fri, 22 Jul 2005 09:12:37 +0900, YAMAMOTO Mitsuharu [EMAIL 
 PROTECTED] said:

 Quote from http://developer.apple.com/qa/qa2001/qa1193.html:

   SwapQDTextFlags(kQDUseCGTextRendering) without kQDUseCGTextMetrics
   only if compatibility with existing documents is required (to avoid
   reflow). The old QuickdrawText metrics are derived from the
   instructed (grid-fitted) outlines, and are sometimes too different
   from the ideal (unhinted) metrics corresponding to the ideal
   outlines used by CG text rendering.

 But the use of kQDUseCGTextMetrics was already rejected.  (Note that
 Emacs 22 stood for the Unicode branch at that time.)

   http://lists.gnu.org/archive/html/emacs-devel/2005-01/msg00635.html


 On Wed, 28 Sep 2005 20:13:27 +0900, Miles Bader [EMAIL PROTECTED] said:

 (the mac text api thing seems to be well known; from the messages
 I've seen posted here, apparently things are screwy enough that it's
 not going to change tomorrow).

A good news is preliminary ATSUI support has just started to work on
my side.  A bad news is it brings some problems with the current
vertical overlap handling that are visible only on anti-aliased
environment.

 YAMAMOTO Mitsuharu
[EMAIL PROTECTED]


___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug