Michael Cadilhac <[EMAIL PROTECTED]> writes:
> In French, this differentiation makes no sense, so I'm wondering if
> fill-french-nobreak-p could be modified to avoid this (I will have a
> look tomorrow if nobody does).
See `sentence-end-double-space', `colon-double-space', etc.
--
Romain Franco
On Mon, 24 Oct 2005 01:45:46 +0200 [EMAIL PROTECTED] (Kim F. Storm) wrote:
> Stephen Berman <[EMAIL PROTECTED]> writes:
>
>> I tried to do this. Fgarbage_collect is called at several places in
>> the Emacs C sources, but I assume you mean the invocation in alloc.c,
>> so that's where I put the br
In article <[EMAIL PROTECTED]>, Zhang Wei <[EMAIL PROTECTED]> writes:
> I got the following error message while I try to read utf-7 encoded email.
> Error during redisplay: (void-function utf-7-post-read-conversion)
> mm-decode-body: Wrong type argument: wholenump, nil
Thank you for the bug repor
In article <[EMAIL PROTECTED]>, Michael Cadilhac <[EMAIL PROTECTED]> writes:
>Hi !
>I'm wondering how I'm supposed to use isearch with a postfix input
>method.
>Let's say I've buffer that contains
>hello, world !
>I'm at (point-min) with a postfix input method. I C-s
Kenichi Handa <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]>, Michael Cadilhac <[EMAIL PROTECTED]> writes:
>
>>Hi !
>>I'm wondering how I'm supposed to use isearch with a postfix input
>>method.
>
>>Let's say I've buffer that contains
>
>>hello, world !
>
>>
I changed this deliberately because red is hard to read on a tty.
So please consider the question closed.
___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Run till exit from #0 Ffuncall (nargs=2, args=0xbfe57660) at eval.c:2870
Fbyte_code (bytestr=144421571, vector=144365692, maxdepth=9) at
bytecode.c:692
692 break;
Value returned is $2 = 137379905
(gdb) finish
Run till exit from #0 Fbyte_code (bytestr=14442
> Indeed. I've mentioned already a few times that the functionality
> offered by font-lock-syntactic-keywords should be added to syntax.el
> (which means make it independent from font-lock) after which
> font-lock-syntactic-keywords can be made obsolete.
> Would you like to implem
>`C-\ C-\' is especially useful inside an incremental search, because
> it stops waiting for more characters to combine, and starts searching
> for what you have already entered.
> Though, I admit that it's not convenient. We long ago
> discussed about a way to improve the behaviour of isearc
David Reitter <[EMAIL PROTECTED]> writes:
> When a popup menu is opened (for example with C-mouse-1 or S-mouse-1)
> and closed by clicking somewhere else, it seems like an extra mouse
> event is sent.
>
> This can cause the point to be set, the region to be removed or
> extended and what not - all
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug@gnu.org mailin
>> In French, this differentiation makes no sense, so I'm wondering if
>> fill-french-nobreak-p could be modified to avoid this (I will have a
>> look tomorrow if nobody does).
>
> See `sentence-end-double-space', `colon-double-space', etc.
IMO, setting the language environment should also adjust
The statements marked ^^^ seem to conflict:
parse-partial-sexp is a built-in function in `C source code'.
(parse-partial-sexp from to &optional targetdepth stopbefore oldstate
commentstop)
...
Value is a list of ten elements describing final state of parsing:
...
In article <[EMAIL PROTECTED]>, Michael Cadilhac <[EMAIL PROTECTED]> writes:
>> `C-\ C-\' is especially useful inside an incremental search, because
>> it stops waiting for more characters to combine, and starts searching
>> for what you have already entered.
>>
>> Though, I admit that it'
> When you type "o", isearch searches for "o" even if "o" is
> not yet fixed. Then when you type, for instance, "'", "ó"
> is searched for from the first search position, and move
> point to the found position regardless of that position
> being before or after the previously found "o". So, isear
Quail input methods produce unexpected results on unfinished input
sequences. For example, consider the input method `cyrillic-translit'
which contains among other rules:
("sh" ?ш) ("shch" ?щ)
Now both "sh" and "shch" work right, but the input sequence "shc" does not.
It inserts two characters:
>>> In French, this differentiation makes no sense, so I'm wondering if
>>> fill-french-nobreak-p could be modified to avoid this (I will have a
>>> look tomorrow if nobody does).
>>
>> See `sentence-end-double-space', `colon-double-space', etc.
> IMO, setting the language environment should also
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug@gnu.org mailin
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug@gnu.org mailin
Symptoms:
I am editing in a CVS tree and getting this happening
-rwxrwxr--1 warrend borg10800 Oct 19 12:56 masterModList*
-rwxrwxr--1 warrend borg10444 Oct 14 10:41 masterModList.~1.85.~*
I see that this version of emacs has this functiionality but as far as I can
tell
Hi,
With the most recent Emacs CVS, NOMIYA Masaru reported he cannot
delete the region that is made by dragging the mouse, using DEL
key. I also confirmed Emacs 21.4 works but 22.0.50 doesn't.
Not much many people might not know such a function, though (and
I was not an exception). Isn't it a si
> With the most recent Emacs CVS, NOMIYA Masaru reported he cannot
> delete the region that is made by dragging the mouse, using DEL
> key. I also confirmed Emacs 21.4 works but 22.0.50 doesn't.
> Not much many people might not know such a function, though (and
> I was not an exception). Isn't it
In article <[EMAIL PROTECTED]>, Juri Linkov <[EMAIL PROTECTED]> writes:
> Quail input methods produce unexpected results on unfinished input
> sequences. For example, consider the input method `cyrillic-translit'
> which contains among other rules:
> ("sh" ?ш) ("shch" ?щ)
> Now both "sh" and "
23 matches
Mail list logo
