before the closing paren, because those are
> the rules of the Info files. If you look in the emacs-* files with a
> pager, you will see that a @pxref with more than one argument always
> ends in a period, no matter if it's the in the same or another manua
x27;\xd0c9\x5397d)}]*"
+(if sentence-end-double-space
+"\\($\\| $\\|\t\\| \\)" "\\($\\|[\t ]\\)")
+"\\|[" sentence-end-without-space "]+\\)"
+"[ \t\n]*"))
! new value using the minibuffer a second time (you can insert the old
! value into the minibuffer for editing via @kbd{M-n}). For example,
@example
M-x set-variable @key{RET} fill-column @key{RET} 75 @key{RET}
--
Juri Linkov
http://ww
oves point to the next occurrence of the search string
and highlights it.
Having a delay in the minibuffer between typing C-s and seeing the search
string highlighted, or requiring to type another key to exit the delay,
would be a nuisance.
--
Juri Linkov
http
> http://www.w3.org/TR/html4/intro/sgmltut.html#h-3.2.2
> "By default, SGML requires that all attribute values be delimited
> using either double quotation marks (ASCII decimal 34) or single
> quotation marks (ASCII decimal 39). ... In certain cases, authors
> may specify the value
oes the same in .emacs. But it seems there is no need.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
-to-save nil
"List of major modes whose buffers should not be saved."
:type '(repeat symbol)
:group 'desktop)
--- 306,314
:type 'regexp
:group 'desktop)
! ;; We skip TAGS files to save time (tags-file-name is saved i
tch doesn't display the search prompt at all for successful search state.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
at contains:
degKK # "Degrees Kelvin" is forbidden usage.
i.e. it defines degK, but has a warning about its usage in comments.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@
Current rules of recognizing HTML files in Emacs are too strict:
1. The valid string delimiter for HTML attribute values is the
quotation character. However, some HTML files on the Web use
apostrophes, e.g.
The program that generates such non-standard meta headers is identified
as 'Microsoft D
(when coding
> (insert (format "coding: %s\n"
> (symbol-name buffer-file-coding-system
> (dolist (v variables)
> (insert (format "%s: %S\n" (symbol-name v) (symbol-value v
> (insert "End:\n")
> (comment-region (mark) (point
As Stefan already pointed out recently, comment-region should be
wrapped with an appropriate let binding of comment-style.
> --8<---cut here---end--->8---
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
n Debian GNU/Linux after removing gzip and
trying to open a compressed file looks like:
Error while executing "gzip -c -q -d < filename.gz"
/bin/sh: gzip: command not found
It seems it is already quite informative.
--
Juri Linkov
h
m"
(lambda () (interactive) (switch-to-buffer "*Messages*")))
;; how to allow using the same key binding in isearch-mode:
(define-key isearch-mode-map "\M-m"
'isearch-other-control-char)
This doesn't cause the reported problem.
--
Juri Li
(format "%S" (symbol-value var
(list var val current-prefix-arg)))
(and (custom-variable-p variable)
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
(name)
--- 2825,2832
(car (car Info-index-alternatives))
(nth 2 (car Info-index-alternatives))
(if (cdr Info-index-alternatives)
! (format "(`,' tries to find %s next)"
! (1- (length Info-index-alternatives)))
file is
not a good idea. But you can still leave insert-file-contents with
let-binding ((auto-compression-mode t)) around it, because compression
mode can handle compressed files on low-level file functions (including
insert-file-contents).
--
Juri Linkov
http://www.jurta.org/emacs/
riginal-minibuffer-message-timeout
! minibuffer-message-timeout
! 2))
! (message ""))
(defun isearch-message-prefix (&optional c-q-hack ellipsis nonincremental)
;; If about to search, and previous search regexp was invalid,
--
Juri Linkov
5,301
;; (ftp) files because they require passwords and whatnot.
;; TAGS files to save time (tags-file-name is saved instead).
(defcustom desktop-buffers-not-to-save
! "\\(^nn\\.a[0-9]+\\|\\.log\\|(ftp)\\|^tags\\|^TAGS.*\\)$"
"Regexp identifying buffers t
variable indicating that the minor
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
its delay after typing C-r
and before point moves to the next occurrence is too long. Sorry.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
t to the
minibuffer contents. For example, with the minibuffer:
Eval: (setq foo 'bar)
typing `C-s foo' will display:
Eval: (setq foo 'bar) [I-search backward: foo]
and `foo' will be highlighted in `isearch' face, as usual.
--
Juri Linkov
http://www.jurta.org/e
, then to print as many keys as many of them
fits into this limit. For example:
M-x scroll-left-> defines the maximum 15 characters
C-next, C-x < -> both keys fit into 15-characters limit,
so replace \[scroll-left] with both keys
--
Juri Link
l' returns the first keybindings. Since
it's not possible to control which keybinding `where-is-internal'
returns, to reproduce this bug `C-x `' should be unbound globally,
e.g. by (define-key ctl-x-map "`" nil). After that
(key-description (where-is-internal &#x
e-excursion
!(skip-chars-backward " ")
!(and (eq (preceding-char) ?.)
! (not (progn (forward-char -1) (looking-at (sentence-end))
;; Don't split a line if the rest would look like a new paragraph.
(unless use-hard-newlines
(save-excu
's
better to leave the current default behavior (with only adding user
input to the history) unchanged.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
deleting the code (I don't know if there are users
still using it), so I only deleted the menu item "Edit" and its
description from the docstring of `Info-mode'.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel
With all rearrangements completed in info.texi, perhaps someone should
proof-read the Info manual before removing the corresponding to-do item
from FOR-RELEASE?
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel
at the top.
There are quite many places in the Emacs documentation where these
commands (and their underlined output) are in the middle of a node.
I don't know is it bad style or what.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-d
;; Don't split a line if the rest would look like a new paragraph.
(unless use-hard-newlines
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
e-name-history)
(if history-delete-duplicates (delete buffer-file-name file-name-history))
(setq file-name-history (cons buffer-file-name file-name-history
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs
this change. OTOH, the artificial case you
described in another mail (the word BOX with asterisks around it) is
extremely rare in the large Info base I looked at.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
default value
of `sentence-end'. There are functions like `fill-delete-newlines'
that rely on its current default value, so changing the default value
of `sentence-end' will break such functions.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
dded to the node "Add" after the following sentence:
However, if you want to edit an Info file manually and
install it manually, here is how.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
tion-ignored-extensions?
BTW, there is "CVS/" in completion-ignored-extensions by default,
but no "RCS/" and ",v". Should these extensions be added too?
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing
very package (e.g. dired.el, recentf.el) could add
their own user-level command names to such a variable.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
s. I suggest to remove .pdf and .dvi
from the default value dired-omit-extensions.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
e
splash screen) is looking to the left. Such difference causes a
discomforting feeling of the icon image being mistakenly mirrored.
Could you turn its head to the same direction?
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
sentence-end)
tries to match the end of the sentence, but fails.
One solution is to fix the regexp in `sentence-end' to match three
periods. However, this might have an undesirable effect in other places.
A more localized fix is to change the rule above to skip only one period
backw
')? If so, then
I think it is safe to fix that in a way of comparing their lengths
before highlighting.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
{} on a filled line
x...
thus not breaking `x...'?
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
;; If there are at least 10 lines with a leading TAB, use TABs.
>(re-search-forward "^ " (+ (point) 10) t 10)))
> (set (make-local-variable 'indent-tabs-mode) t
Good heuristic.
--
Juri Linkov
http://www.jurta.org/emacs/
_
ome modes
should override this value with a new variable like `local-variables-prefix'.
Also the local variables list for `dcl-save-all-options' is not general.
A better choice is a list like used by desktop.el to save the values of
local variables in the desk
isting Local-Variables sections,
but for new sections adding these special variables would be easy
with a new command (from etc/TODO) that will make a local variables
section and write the values of `local-variables-prefix' and
`local-variables-suffix' automatically.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
it to a value that
matches the Local Variables section only inside HTML comments, and such
problems of mistakenly using a Local Variables section wouldn't occur
in packages that convert files to other representations.
--
Juri Linkov
http://www.jurta.org/emacs/
__
n". But what to do with the second sentence? Commands that
read buffer names still put the default after the colon.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
"\\)")
buffer-file-name))
(setq indent-tabs-mode t)))
(add-hook 'find-file-hooks 'indent-tabs-mode)
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
box or pop-up menu, because the terminal does not
--- 269,275
@code{last-nonmenu-event} to a suitable value around the call.
@end defun
! @defun message-box format-string &rest arguments
This function displays a message like @code{message}, but uses a dialog
box (or a pop-up m
ult value of ispell-aspell-supports-utf8 could be
`auto-detect', so users will be able to set it explicitly to `nil' or `t',
if version testing fails (with `condition-case' around the testing code).
--
Juri Linkov
http://www.jurta.org/emacs/
_
g are clearer than "initial": "init-val", "init-value",
> "initial-value".
As there exist already only three different argument names: "initial",
"initial-contents" and "initial-input", I'd choose one of existing names
inst
han "initial" or "default". To understand the
difference between them, programmers still should consult the documentation.
> "Init" clearly stands for "initial", but the "value" part is
> important - "initial" by itself doesn't
is to save space.
If the meaning of "hist" is as clear as "history", then it could
be used consistently in other functions as well.
> require-match, mustmatch, must-match, existing
>
> This seems like a good case
> Juri Linkov <[EMAIL PROTECTED]> writes:
>
>> Since `default' is a keyword in C, `defaults' is a good replacement.
>
> `default' is special cased: you can spell it `defalt' in the C code and
> still get `DEFAULT' in the doc string.
Thanks f
-20050121")
version<("0.60.3-20050121" "0.60")
ispell-check-version()
ispell-init-process()
ispell-buffer-local-words()
ispell-accept-buffer-local-defs()
ispell-word(nil nil nil)
call-interactively(ispell-word)
--
Juri Linkov
http://www.jurta.org/emacs/
; is twice shorter than `inherit-input-method' and the `IM'
abbreviation is already mentioned in the Emacs manual.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
hat
> closer to their origin.
>From my experience, quite contrary: for a half year I got no crashes
with a low value of gc-cons-threshold. But when I increased it to
a big value (80MB) I immediately got a cons_free_list related crash.
--
Juri Linkov
> Here's a slightly corrected new patch.
> Please try this instead of the previous one.
It works for all my tests.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailm
argument stringp nil)
expand-file-name(nil)
compilation-find-file(# "ChangeLog" nil)
compilation-next-error-function(0 nil)
next-error(0)
compile-goto-error(return)
call-interactively(compile-goto-error)
--
Juri Linkov
http://www.jurta.org/emacs/
___
xtract the directory name from the string:
make: Entering directory `{absolute directory of source tree}/emacs/lisp'
and use it even for files located in subdirectories of `emacs/lisp'.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs
rompt-default-format " [%s]: ")
(read-buffer "Buffer name: " "foo" t)
will display the prompt:
Buffer name [foo]:
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
ough this function
returns an empty string. I don't know whether this should be fixed or
maybe it causes no problems.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
7;s response to your message seems right, but his reconstruction
of your message is not. Could you confirm that you really meant this:
But I think it would be more convenient to [use M-n to]
access [additional default values] from the list [of default values].
--
Juri Linkov
http:/
echo area, or inserted into the buffer) contains
a literal newline instead of `\n'. So after evaluating examples from
the manual users will see different results when examples of output
contain `\n' in the manual, and the real displayed output contains
literal newlines.
--
Juri Linkov
ht
default values is M-n. It could work like M-p for a list of history
values, but in the opposite direction.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
setq regexp-search-ring-variable 'regexp-history)
or:
(setq regexp-history-variable 'regexp-search-ring)
(setq regexp-search-ring-variable 'regexp-search-ring)
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
all these default
values accessible in the minibuffer via M-n.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
toggles a literal newline
or `\n' in return values, or even to fill a bug report.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
x0817af28 in create_process (process=141365940, new_argv=0xbfffe954,
current_dir=140249731) at process.c:2153
#4 0x0817a97d in Fstart_process (nargs=5, args=0xbfffea94) at process.c:1695
...
(gdb) fr 3
#3 0x0817af28 in create_process (process=141365940, new_argv=0xbfffe954,
current_dir=140249731)
that the
difference whether a function returns or prints a literal newline or
`\n' is preserved in the Emacs Lisp Reference Manual.
Since `thing-at-point' actually returns a literal newline instead of
`\n', it would be more correct to
roc) 'run))
(process-send-eof proc))
(set-process-sentinel proc 'compilation-sentinel)
(set-process-filter proc 'compilation-filter)
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
t) t)
;; Set `font-lock-lines-before' to 0 to not refontify the previous
;; line where grep markers may be already removed.
(set (make-local-variable 'font-lock-lines-before) 0))
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
tory where compilation
was started. I think `-*- default-directory: "..." -*-' in the first
line should be changed to `-*- compilation-directory: "..." -*-'.
Currently this doesn't work with `compilation-directory' in the first
line, but it is easy to fix co
ground color (or background color,
respectively) of face @var{face}, as a string.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
e causes questions, maybe it should be mentioned in
>> etc/NEWS?
>
> Definitely.
In which NEWS section would you expect to find this fix?
Possible candidates:
* Lisp Changes in Emacs 22.1
** Face changes
or
* Incompatible Lisp Changes in Emacs 22.1
or
* Incompatib
ine-p))
+ (define-obsolete-function-alias 'set-face-underline
+ 'set-face-underline-p "22.1")
+
(defun set-face-inverse-video-p (face inverse-video-p &optional frame)
"Specify whether face FACE is in inverse video.
--
J
an old or new Emacs version):
(set-face-inverse-video-p 'mode-line t)
(set-face-foreground 'mode-line "red")
and see that this behavior is exactly the same as on ttys now.
Since this change causes questions, maybe it should be mentioned in
etc/NEWS?
--
Juri Linkov
http://www.
to display the prompt text.
@item fringe
! @cindex @code{fringe} face
The face for the fringes to the left and right of windows on graphic
displays. (The fringes are the narrow portions of the Emacs frame
between the text area and the window's right and left borders.)
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
at I did.
What do you expect in this situation? Trying to delete a character at
bob prints the message "Beginning of buffer". Perhaps it should print
something like "Beginning of prompt input area" in the minibuffer.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
cult to move point into the
prompt area by default? For example, to disable moving point into
the prompt with C-b, but allow C-a at the beginning of the input
area to move point to the beginning of the prompt. This is like C-a
(`message-beginning-of-line') works on message header fields.
he grep process that helps you
to discover your mistake.
Maybe grep.el should try to parse the grep command line and warn the
user about a missing file name (e.g. by highlighting the command in
the grep buffer in `compilation-error' face). This helps to notice
the mistake sooner, bu
I can send a small patch that implements this.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
>> Would somebody please install the following change:
>>
>> 2005-08-13 Alan Mackenzie <[EMAIL PROTECTED]>
>>
>> * search.texi: Correct a typo.
>
> Done, thanks.
Wouldn't it be better to ispell-check the whole Info manual than t
tring'.
>
> I agree, see my corrected patch below.
Thanks. Please see the recent discussion on emacs-pretest-bug.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
these manuals
between each other before the release would be enough - I see
no reason for the text about regexps to be different in both manuals.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
ame changed to EMAKS :-)
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
e. C-SPC is useful in the
minibuffer to set mark.
A better replacement key binding for minibuffer-complete-word would be
S-TAB (but not M-TAB because it can be useful to complete symbols
in the minibuffer from the external table).
--
Juri Linkov
http://www.jur
ur nodes.
Then in the Emacs Lisp Reference Manual only the node
(info "(elisp)Regexp Functions") would remain with a cross-reference
to the Emacs User Manual for description of regular expressions.
--
Juri Linkov
http://www.jurta.org/emacs/
erface for performing
different actions on exit? Maybe to use a prefix argument, e.g.:
`M-1 RET' - don't remove highlighting
`M-2 RET' - don't push the search string into the search ring
`M-3 RET' - leave point at the beginning of the found string
And how to combine them? M
(emacs)Format Colors")
31 (info "(emacs)Charsets")
31 (info "(emacs)Borders X")
31 (info "(emacs)Abbrevs")
31 (info "(elisp)Window Type")
31 (info "(elisp)Warning Options")
31 (info "(elisp)Variables with Restricted Values")
31 (inf
tional component of "Time", anyway.
Ok, I agree.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Search Text
Search Index
Go to node
Choose menu subtopic
Create Info buffer
Emacs Info Variables
Expert Info
Edit
Add
Menus
Cross-refs
Help-Cross
Tags
Checking
Creating an Info File
Index
--
ithout pushing the search string
into the search ring. Very useful to not stuff the search history
with unnecessary search strings.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
to turn it off (there is find-file-literally to visit compressed files
without decompression).
The Option menu is too big already, so removing an unnecessary item is
a good change.
--
Juri Linkov
http://www.jurta.org/emacs/
___
Emacs-devel mailing l
(such as Note: and Menu: tags), but that 2)
> users searching Info should not find such tags (they can always find them
> using the appropriate Info commands, such as Info-next-reference).
I have a small uninstalled patch that fixes this problem trivially.
Is it ok to install it?
--
Juri Link
a line
((lambda ()
(setq compilation-error-screen-columns nil)
(- (match-beginning 4) (match-end 1)))
.
(lambda () (- (match-end 5) (match-end 1)
(- (match-end 4) (match-beginning 4)
nil 1)
But it still doesn't fontifify grep matches
bprocess.
! @end table
!
! @findex grep
! To run @code{grep}, type @kbd{M-x grep}, then enter a command line that
specifies how to run @code{grep}. Use the same arguments you would give
@code{grep} when running it normally: a @code{grep}-style regexp
(usually in single-quotes to quote the sh
l"
This menu item is too wide.
A more shorter and still understandable menu item is:
"Time, Load and Mail"
or with `or':
"Time, Date, Load or Mail"
> !
e duplicated in both nodes. It would be better to provide this
information only in the Emacs User Manual, and to make a cross-reference
to it from the Emacs Lisp Reference Manual.
I could create a patch for that by merging the text from both nodes
into `(emacs)Standard Faces', if this is
Cross-refs
Help-Cross
Tags
Checking
Creating an Info File
Index
--
Ju
pattern ":[0-9]+:" or ends with the pattern ":[0-9]+" (like Juri's example)
> Juri, wouldn't be good to add a comment about this in grep.el or grep.txt?
Since Richard doesn't want to document even `-n' option in grep.el,
I am not sure I can add a comment i
> I believe that S-Tab still does not move backwards. It did at some time,
> but have been changed again.
Could you be more specific on what version/platform it doesn't work.
On GNU/Linux with the latest CVS, S-TAB works in help buffers
(but not M-TAB, ESC-TAB or C-M-i).
--
Juri
1 - 100 of 318 matches
Mail list logo
