[ I already sent this yesterday (via Gmane), but apparently it didn't
make it to the list ([EMAIL PROTECTED]).
Sorry if you get it twice. ]
`M-x report-emacs-bug' wrote:
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
I have the following locale
Dear Richard,
Thank you for pointing out debug-on-entry to me.
This seems to be the easiest solution if I find other
new problems with pretest version concerning old elisp libraries
that are OUTSIDE the standard distribution.
I no longer have to load the emacs lisp source file and interactively
Hello.
If I set c-backslash-column to 79, I don't get backslahses at column 79, but
at column 72. Cc-mode silently truncates the column to an even tab-width. I
could not find any documentation on this behaviour, nor is there any way to
turn it off, so I can get backslashes at column 79.
Prepare a file containing a Czech e-with-a-hook character (followed
by a newline) in Windows 1250 encoding:
$ printf \354\n /tmp/file.txt
Ensure DISPLAY is set, and run Emacs:
$ emacs -Q
Tell Emacs to prefer the Windows 1250 coding system:
M-x eval-expression RET (prefer-coding-system
Note that the yanked copy is different than the text we copied. It
shows up as a '?' character.
I've tracked the bug down to 2 lines in lisp/term/x-win.el:
In x-select-text():
;; ICCCM says cut buffer always contain ISO-Latin-1
(encode-coding-string text 'iso-latin-1)
In
Note that the yanked copy is different than the text we copied. It
shows up as a '?' character.
I've tracked the bug down to 2 lines in lisp/term/x-win.el:
In GNU Emacs 22.0.91.4 (i686-pc-linux-gnu, GTK+ Version 2.8.20)
of 2006-11-19 on chrislap
2006-11-20 Jan Djärv [EMAIL
Does this change give good behavior?
*** files.el13 Nov 2006 15:19:14 -0500 1.865
--- files.el21 Nov 2006 21:30:29 -0500
***
*** 4081,4086
--- 4081,4091
File %s no longer exists!
Cannot revert
Well, it's simple enough for Emacs to generate, but if it's a constant
strings, it's easier for the other process to recognize it.
It is easy to recognize (comint.
Please don't exaggerate these minor problems.
___
emacs-pretest-bug mailing
| ** The key ESC has been rebound, but you can use instead [More
information] **
`
I fail to understand what but you can use instead means.
Is that because the value is nil? I think that case needs to be
handled specially. It can say just The key ESC has been rebound,
so you
Is this in fact the case, for the default case table of Emacs unicode
2 branch, when the change I made for dotless i is installed there?
Your change is not yet propagated to emacs-unicode-2 branch.
is there any reason not to propagate it there?
If it will be propagated, that will
A similar bug was fixed some days ago, make sure your CVS is up to date.
Jan D.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
On Wed, Nov 22 2006, Richard Stallman wrote:
| ** The key ESC has been rebound, but you can use instead [More
information] **
`
I fail to understand what but you can use instead means.
Is that because the value is nil? I think that case needs to be
handled specially.
Reiner Steib [EMAIL PROTECTED] writes:
I think summarizing the problematic keys _at the very beginning_ of
the tutorial or in a splash screen at it's startup would be much
better than interrupting the tutorial text several times in the middle
of a sentence.
hand.
Richard Stallman [EMAIL PROTECTED] writes:
Well, it's simple enough for Emacs to generate, but if it's a constant
strings, it's easier for the other process to recognize it.
It is easy to recognize (comint.
Please don't exaggerate these minor problems.
It would be even easier for a
Reiner Steib [EMAIL PROTECTED] writes:
I think summarizing the problematic keys _at the very beginning_ of
the tutorial or in a splash screen at it's startup would be much
better than interrupting the tutorial text several times in the middle
of a sentence.
Suggestion: Let's keep the colors
Well, it's simple enough for Emacs to generate, but if it's a constant
strings, it's easier for the other process to recognize it.
It is easy to recognize (comint.
Please don't exaggerate these minor problems.
I'm not saying it's hard. Just that it is easier for people to adapt to
uname -a gives:
Linux hostname 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT
2006 i686 i686 i386 GNU/Linux
I checked out the unicode branch with tla and ran
./configure --with-gtk --enable-font-backend --with-xft
make bootstrap
which fails complaining about undefined symbol this_pos_byte
This has been fixed. Update, rebuild and try it again.
Thanks Nick, that fixes it. I should have tried updating before reporting
the bug.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
On 11/22/06, Richard Stallman [EMAIL PROTECTED] wrote:
Does this change give good behavior?
*** files.el13 Nov 2006 15:19:14 -0500 1.865
--- files.el21 Nov 2006 21:30:29 -0500
***
*** 4081,4086
--- 4081,4091
File %s no longer
Sorry, I made a mistaken. Should use encode-coding-string rather than
decode-coding-string.
On Thu, 23 Nov 2006 00:02:22 +0800, Chong Yidong [EMAIL PROTECTED]
wrote:
The hexl-max-address usually set to buffer-size, but when the buffer
contain a multiple byte character or the file
But from the lusers's point of view, it would be nice to
have a guideline of how to move over to newer and more powerful
libraries/packages such as jit-lock from lazy-lock.
(Info doesn't seem to have been updated...
Would you please be more specific?
Please show the text that
Sorry for the mistaken. And I found that use file size may cause some
error because the buffer may be modified.
This my patch:
diff -utbB /home/ywb/lisp/hexl.el /home/ywb/lisp/hexli.el
--- lisp/hexl.el2006-10-30 14:47:26.0 +0800
+++ lisp/hexli.el 2006-11-23
22 matches
Mail list logo