The link to Extended Menu Items in the doc string for define-key is broken.
I think the reason is that it fails to specify which manual.
Please try adding `(elisp)' to the node name.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http
(progn (new-frame)
(redisplay t)
(x-popup-dialog t '("Foo" ("Bar" . 1
I tried this but it didn't fail -- the new frame was not empty.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailma
Thanks.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
For now, I installed the flyspell change. I suggest we think about the
wider issue after the release.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
On Wed, 2007-04-11 at 23:23 +0200, martin rudalics wrote:
> > I set it in custom-set-variables; another likely scenario, I would think.
>
> whitespace.el has this form
>
> (defcustom whitespace-check-indent-whitespace indent-tabs-mode
>
> which, as Miles explained, gets evaluated when whitespac
Richard Stallman wrote:
> I think this is an issue for aspell or ispell (whichever one you are
> using). Not for Emacs.
No, I think rather that flyspell should downcase abbrevs before
defining them, like define-mode-abbrev does.
Beyond that, given the way expand-abbrev treats case, does it make
I think this is an issue for aspell or ispell
(whichever one you are using).
Not for Emacs.
thanks for the prompt response. actually I thought this might be an issue
of dabbrev and emacs. flyspell is only the way in which the abbrev is
defined in my bug report.
So if I create an abbrev suc
The variable pending-undo-list is used by for example undo-start and
undo-more. The doc strings says that you should first call undo-start
and then you can call one or several times undo-more later.
If those calls are done in different buffers it looks like trouble to
me. Should not pending-un
Please install your patch.
Done.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
(1) revert-buffer does not work in *Locate* buffers that result from
C-u locate RET or C-u locate-with-filter RET.
Note that, without my very latest suggested patch, you _can_ actually
correctly revert such buffers using `C-u g'. Obviously, this is not a
very clean feature. (But it is fu
Richard Stallman wrote:
(2) While C-u locate RET gives the prompt "Run locate (like this): ",
locate-with-filter gives the same prompt, "Locate: ", regardless of
whether or not a prefix arg is used. The behaviour of C-u
locate-with-filter is analogous to C-u locate
Johan Bockgård wrote:
> The doc string for dired-virtual-mode speaks about the nonexistent
> variable `buffer-contents-mode-alist'. Also, the regexp is wrong (the
> "/?+" part) and a bunch of backslashes are missing.
Thank you; installed.
___
emacs-p
(1) revert-buffer does not work in *Locate* buffers that result from
C-u locate RET or C-u locate-with-filter RET.
We have not generally implemented reverting for search command output.
Locate implements a revert-buffer-function, locate-update.
The reported bug can be annoying
"Lennart Borgman (gmail)" wrote:
> The link to Extended Menu Items in the doc string for define-key is broken.
Thanks; fixed.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
You have found a real bug.
Please install your patch.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
> What's the reason for disregarding my legal concerns about that
> work?
Maybe this message is meant for some specific recipients who will
already know what this is about. If not, please could you explain in
more detail what you mean? Precisely which work has potential legal
(1) revert-buffer does not work in *Locate* buffers that result from
C-u locate RET or C-u locate-with-filter RET.
We have not generally implemented reverting for search command output.
(2) While C-u locate RET gives the prompt "Run locate (like this): ",
locate-with-filter gi
I will try to improve this.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
I think this is an issue for aspell or ispell
(whichever one you are using).
Not for Emacs.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
On Sat, Apr 21 2007, martin rudalics wrote:
>> [subr.el]
>> ;; These are the XEmacs names:
>> (defalias 'point-at-eol 'line-end-position)
>> (defalias 'point-at-bol 'line-beginning-position)
>
> I think it's for Emacs < 20 compatibility.
I think the comment is correct. XEmacs prefers point-at-[b
The doc string for dired-virtual-mode speaks about the nonexistent
variable `buffer-contents-mode-alist'. Also, the regexp is wrong (the
"/?+" part) and a bunch of backslashes are missing.
2007-04-21 Johan Bockgård <[EMAIL PROTECTED]>
* dired-x.el (dired-virtual-mode): Doc fix.
***
`read-number' should have a doc string.
Ok, thanks.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
>>Here are other incorrect uses of kill-* functions in lisp/progmodes:
>>
>>cc-cmds.el:859: (kill-region (progn (forward-line 0) (point))
>>perl-mode.el:653: (kill-region (point) eol))
>>
>>And there's a bunch of suspicious kill-line/kill-word/kill-region in
>>man
hello, I don't know if this is a bug or some option that I need to set, but
it's been there for a while:
emacs-22.0.98 on gnu-linux redhat
emacs -Q
open a new file t.txt
turn flyspell on
set flyspell-abbrev-p to t
type
Cho
the word is highlighted as a spelling mistake. use middle mouse to save
The bottom part of (info "(elisp) Extended Menu Items") is badly
formatted which makes it quite hard to understand. The very last
paragraph should belong to :filter.
In GNU Emacs 22.0.98.1 (i386-mingw-nt5.1.2600)
of 2007-04-19
___
emacs-pretest-
cc-mode doesn't like `line-beginning-position' and
`line-end-position'.
[subr.el]
;; These are the XEmacs names:
(defalias 'point-at-eol 'line-end-position)
(defalias 'point-at-bol 'line-beginning-position)
I think it's for Emacs < 20 compatibility.
___
[EMAIL PROTECTED] (Johan Bockgård) writes:
> Here are other incorrect uses of kill-* functions in lisp/progmodes:
>
> cc-cmds.el:859: (kill-region (progn (forward-line 0) (point))
> perl-mode.el:653: (kill-region (point) eol))
>
> And there's a bunch of suspicious
The link to Extended Menu Items in the doc string for define-key is broken.
In GNU Emacs 22.0.98.1 (i386-mingw-nt5.1.2600)
of 2007-04-17
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretes
martin rudalics <[EMAIL PROTECTED]> writes:
> cc-mode doesn't like `line-beginning-position' and
> `line-end-position'.
[subr.el]
;; These are the XEmacs names:
(defalias 'point-at-eol 'line-end-position)
(defalias 'point-at-bol 'line-beginning-position)
Here are other incorrect uses of kill-*
> Chong Yidong writes:
> Thanks. I've checked the patch in.
(I see Luc made further changes.)
There are still a few problems:
(1) revert-buffer does not work in *Locate* buffers that result from
C-u locate RET or C-u locate-with-filter RET.
(2) While C-u locate RET gives the prompt "R
> With my recent cvs build or the debian snapshot, and starting from
> "emacs -Q", visiting the file foo.c below with
>
>C-x C-f foo.c
>
> leaves the first line in the kill ring,
>
>C-y
>=> inserts "/* hello */
>
> where I hoped it would leave the kill ring alone. (In particular it's
Sorry for not answering earlier but I just retrieved your response from
gmx's spam folder.
> So, what is now the recommended way to set file-specific font-lock
> keywords using file-local variables? If this has changed, it should be
> specified in the NEWS. I can write an entry once I understan
32 matches
Mail list logo
