From: Richard Stallman [EMAIL PROTECTED]
CC: [EMAIL PROTECTED], emacs-pretest-bug@gnu.org,
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Date: Fri, 27 Oct 2006 09:33:35 -0400
There is a big difference between unibyte strings and encoded unibyte
strings.
Date: Fri, 27 Oct 2006 21:25:07 -0400
From: Gilbert Harman [EMAIL PROTECTED]
In the main directory:
configure --without-x --enable-carbon-app
finishes without error, but
make bootstrap does not complete:
You shouldn't need to make bootstrap with this tarball: it already
includes the
Hello!
When I open a text file with a CP1250 contents, mode-line does not
show a specific encoding, it starts with ``-:´´. So I invoke C-x REF
r cp1250 RET – but there does not seem to be change (except that read-
only goes away).
In GNU Emacs 22.0.50.1 (powerpc-apple-darwin8.8.0, X
With cursor inside a functions definition, what should
`defun-at-point' resp. (thing-at-point 'defun) return:
- the function name
- the complete functions corpus
What about introducing `functionname-at-point'?
Thanks
__
Andreas Roehler
___
From: Peter Dyballa [EMAIL PROTECTED]
Date: Sat, 28 Oct 2006 14:38:16 +0200
When I open a text file with a CP1250 contents, mode-line does not
show a specific encoding, it starts with ``-:''. So I invoke C-x REF
r cp1250 RET - but there does not seem to be change (except that read-
According to the unicode standard, #xFF01 .. #xFF60 are fullwidth
ASCII variants and fullwidth brackets, they should be set double
width in the char-width-table.
May be this patch is useable.
*** c:/Emacs/lisp/international/characters.el Thu Oct 26 23:03:06 2006
---
Am 28.10.2006 um 15:55 schrieb Eli Zaretskii:
From: Peter Dyballa [EMAIL PROTECTED]
Date: Sat, 28 Oct 2006 14:38:16 +0200
When I open a text file with a CP1250 contents, mode-line does not
show a specific encoding, it starts with ``-:''. So I invoke C-x REF
r cp1250 RET - but there does not
From: Peter Dyballa [EMAIL PROTECTED]
Date: Sat, 28 Oct 2006 16:40:12 +0200
Don't you see a `*' in the mode line instead of `:'?
Not initially.
It seems that this problem is somehow related to the fact that Emacs
initially visits the file in unibyte mode.
Perhaps we should do this:
*** c:/Emacs/lisp/international/characters.el Thu Oct 26 23:03:06 2006
--- d:/download/emacs--unicode--0/lisp/international/characters.el Sun Oct
29 00:42:10 2006
***
*** 1013,1029
;; 2: East Asian Wide and Full-width characters.
(let
However, if you store encoded text in unibyte strings, you are
responsible for decoding and encoding when necessary. You have to
keep track, everywhere, of whether the data is encoded or not.
It's pretty easy to keep track of it: unibyte == encoded, multibyte
== decoded.
emacs -Q
M-x set-variable mouse-1-click-follows-link RET nil RET
M-x customize-option read-quoted-char-radix RET
Click mouse-1 on the first line, text `read-quoted-char'. This opens
the *Help* buffer with a description of `read-quoted-char'.
With `mouse-1-click-follows-link', I would not expect
11 matches
Mail list logo