>> `compilation-start' needs to check if the process is running
>> before calling `process-send-eof':
>
> That's odd. AFAICT no blobking operation takes place between the
> start-process and the process-send-eof, so the process-status should still
> be `run' no matter how quickly the process exits
> With this change, when grep finishes too quickly (for example, after
> searching in a nonexistent file), `process-send-eof' fails with the
> following error:
> Debugger entered--Lisp error: (error "Process grep not running")
> process-send-eof(#)
> compilation-start("grep -inH -e search file
>>> The customizable variable `font-lock-lines-before' is not honored by
>>> jit-lock mode.
>>
>> I know what that means in therms of what the code does, but I'm wondering in
>> which circumstance it makes a visible difference to the end user.
>> Do you have a test case?
> Suppose not: Wouldn't t
>> > OTOH at a first glance *I* don't expect a control structures such as
>> > `when' to return any useful value when the conditional clause fails.
>> > But maybe I've been doing too much Scheme these days. (no, surely not
>>
>> You're just suffering from one of the many places where Scheme is
>>
For the archives, src/xfaces.c is a good example to look at after
reading the relevant sections of the elisp manual.
I browsed through all of src; of all of the .c files, xfaces.c
deals with an api most similar to what I asked about.
-JimC
--
James H. Cloos, Jr. <[EMAIL PROTECTED]>
_
Because this means that every time I insert one character, redisplay
would refontify `font-lock-lines-before' in addition to the current
line.
Would that be bad?
Whether and when these lines are refontified
would be _also_ decided by the redisplay engine. And the latter doe
[I've moved this thread to emacs-devel as it concerns Emacs in CVS]
> Hi all:
>I am using the gdb-mode in emacs and feel it is terrific nice
> compared with visual studio from microsoft. But I have one question
> about the gud-ui frame. To be more specificly, the problem is the
> locals of xx
What about mentioning, in the Emacs manual section on `case-fold-search',
that there are also other, similar options that control case sensitivity in
different contexts. We could suggest, for instance, that the user do
`apropos-variable' on "case-fold-search" to find them all.
A recent question on
> for `thing-at-point' i see:
>
> @result{} "Gentlemen may cry ``Peace! Peace!,''\n"
>
> which has the `\n' instead of a literal newline. i'd like to change the
> former two to resemble the latter. any objections? any reason to go in
> the opposite direction?
Neither of these functions ret
Emilio Lopes <[EMAIL PROTECTED]> writes:
> But the problem remains: too often I have to first mark a word or symbol,
> copy the region, start a command (`grep', `occur', `query-replace',
> whatever), paste it, press . That's three keystrokes too many.
How about making the thing at point be acces
Stefan Monnier wrote:
>>The customizable variable `font-lock-lines-before' is not honored by
>>jit-lock mode.
>
>
> I know what that means in therms of what the code does, but I'm wondering in
> which circumstance it makes a visible difference to the end user.
> Do you have a test case?
>
>
Suppo
Hi Alan,
Alan Mackenzie writes:
> What is a "paragraph" in Emacs?
The info node that you quoted is (info "(emacs)Paragraphs") I think?
It has this text (this is a rather old CVS version, so it may be
different by now):
[...] Blank lines and text-formatter command lines separate
paragraphs
`compilation-start' needs to check if the process is running
before calling `process-send-eof':
Please install your patch--and thanks.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Can you please clarify the location of the colon? Your update to the
manual says this:
> + Enter value (default 42):
However, "C-x b (switch-to-buffer)" for example shows this:
"Switch to buffer: (default foo) "
You are right. Thanks.
__
which has the `\n' instead of a literal newline. i'd like to change the
former two to resemble the latter. any objections? any reason to go in
the opposite direction?
I agree it is better to make it uniform. Each alternative has an
advantage, so I am not sure which is best. It wou
> I'd point out that fill-nobreak-predicate is a hook in recent
> versions of Emacs
I notice the manual still only says nil or a function. Perhaps
something like the following (new text for ease of reading, diff
below),
Your patch looks good. Would someone please install it?
Hi, Emacs!
What is a "paragraph" in Emacs? I can't find a @dfn{paragraph} anywhere
in the Emacs/Elisp manuals. I don't have the full CVS of Lispref, but
grepping in the released version didn't produce any hits.
There are definitions of the two paragraph regexps in the Elisp Manual:
- Variable
Emilio Lopes <[EMAIL PROTECTED]> writes:
> I think something like isearch's "C-w" and friends extended to other
> commands which read from the minibuffer would be useful.
I would like that.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://list
> (2) Modify `jit-lock-after-change' appropriately by, for example,
inserting
>
>(forward-line (- font-lock-lines-before))
>
> before
>
>(setq start (line-beginning-position))
>
> That seems like the right fix. Why do you think it isn't?
>
>
Because this means that every
> However, the
> associated tags are not assgined a face like `custom-variable-tag'.
>
> I don't understand that sentence at all, sorry.
>
>
Consider, for example, the customization buffer for `matching':
(1) `match' stands out in `custom-face-tag-face', by default scaled by
1.2 and
20 matches
Mail list logo
