Re: Interactive specs, align.el
This change makes repetition of these commands (with `repeat-complex-command') recompute the bounds of the region rather than use the old values of point and mark. I think using `region-beginning' and `region-end' is cleaner than `(max (point) (mark))', but for `repeat-complex-command' this change makes no difference. Neither region-beginning/region-end, nor min/max expression with mark/point is recorded unevaluated in command-history. Perhaps `call-interactively' should be fixed to support `append' to quote region-beginning/region-end inside it, or align.el should be changed to use `list' on its interactive specification. -- Juri Linkov http://www.jurta.org/emacs/ ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: narrow-to-region keybinding
Date: Thu, 08 Dec 2005 13:35:16 -0500 From: Edwin Stearns [EMAIL PROTECTED] The key binding 'C-x nn' for narrow-to-region has been disabled. In what version of Emacs did you see it enabled? At least in 21.4 it was disabled as well, and the manual even mentions this explicitly (in the node Narrowing). ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: CUA mode: C-S-c as prefix does not work
* Kim F. Storm (2005-12-08) writes: Ralf Angeli [EMAIL PROTECTED] writes: ;; - use the SHIFT key with the prefix key, i.e. C-X or C-C The last option does not seem to work (at least with the examples I tried). As an example, Thanks. I have installed a fix. Thanks. I'll go and inform the user who originally reported this. By the way, it would probably be a good idea to move the documentation which can be found in cua-base.el to the Emacs manual which already contains a section about CUA mode. RMS is concerned about the size of the (printed) Emacs Manual, so I think the description of cua-mode in the Emacs manual is sufficient as is (I already expanded it compared to what was there originally). Hm, I think that the stuff about the prefix keys is very useful. It's a pity that it is hidden in the Lisp file. But cua-mode definitely deserves a manual (cua.texi) on its own to describe all of its features. I will probably write it eventually, but if anybody would like to write it (or just start drafting a manual for it), I would appreciate it very much. Of course, I will help as much as I can... If I actually used CUA mode and if I had not enough to do with AUCTeX ... (c; -- Ralf ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
ESC-$ fails on ispell version check
ESC-$ now gives the following error: Debugger entered--Lisp error: (error Invalid version syntax: '.33.7.1 alpha') signal(error (Invalid version syntax: '.33.7.1 alpha')) error(Invalid version syntax: '%s' .33.7.1 alpha) version-to-list(.33.7.1 alpha) version(.33.7.1 alpha 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) This is the version of ispell (really aspell) that came with Redhat 9.0: $ ispell --version Ispell compatibility script for Aspell. Usage: /usr/bin/ispell [options] -a|-l|-v[v]|file $ ispell -v @(#) International Ispell Version 3.1.20 (but really Aspell .33.7.1 alpha) I guess the problem is with version-to-list not accepting the aspell version string. Perhaps it should interpret .n as 0.n ? -- Kim F. Storm [EMAIL PROTECTED] http://www.cua.dk ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: CUA mode: C-S-c as prefix does not work
Ralf Angeli [EMAIL PROTECTED] writes: Hm, I think that the stuff about the prefix keys is very useful. It's a pity that it is hidden in the Lisp file. Agree! I have added a few lines about it to the manual. -- Kim F. Storm [EMAIL PROTECTED] http://www.cua.dk ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: build failure on Irix 6.5/gcc
We are interested...in installing a fix, but there may not be anyone here who uses that system, so we can only wait till someone sends us a fix. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: find-file sometimes doesn't
Richard M. Stallman [EMAIL PROTECTED] writes: In the last week, sometimes maybe 1 in 20 times, C-x C-f (find-file) RET won't find the given file. However, the symptom is that if I'm editing buffer foo, and run find-file to open file bar, instead of getting two equally-sized windows containing foo and bar, I get two foo windows, one of which is only three lines high. Is this reproducible? Yes! If you find a file that is under revision control that you do not have permission to edit, you get the following: Debugger entered--Lisp error: (wrong-type-argument stringp nil) file-symlink-p(nil) vc-find-file-hook() run-hooks(find-file-hook) after-find-file(nil t) find-file-noselect-1(#buffer interfaces /etc/network/interfaces nil nil /etc/network/interfaces (80445 769)) find-file-noselect(/etc/network/interfaces nil nil t) find-file(/etc/network/interfaces t) call-interactively(find-file) Oddly, this alternates. The next time you use C-x C-f on the same file, it succeeds. Kill the buffer and find it again and it fails. The use of revert-buffer on such a read-only buffer fails in the same way every time. If so, can you please debug it? Not completely. I tracked the problem down to find-file-name-handler setting buffer-file-name to nil (maybe that's enough info to remind someone of a change they made in the past couple of weeks). Here's the stack at that time: Debugger entered--returning value: nil find-file-name-handler(/etc/network/interfaces vc-registered) * vc-registered(/etc/network/interfaces) * vc-backend(/etc/network/interfaces) * byte-code(... * vc-find-file-hook() run-hooks(find-file-hook) after-find-file(nil nil t t nil) revert-buffer(t) call-interactively(revert-buffer) execute-extended-command(nil) call-interactively(execute-extended-command) find-file-name-handler is down in C which is beyond my ability to debug. But the recipe is: 1. emacs -q 2. Visit a file that is under revision control and owned by someone else (in my case /etc/network/interfaces is owned by `root' and is checked into Subversion and I'm trying to edit it as `wohler'). 3. If that doesn't bomb out, revert-buffer will. I hope that provides enough info for someone else to debug this readily. -- Bill Wohler [EMAIL PROTECTED] http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Help on font-lock-add-keywords: APPEND is a poor name.
Both Info and the doc string for font-lock-add-keywords name the optional argument APPEND. However, its possible values show that this is a poor name. A better name might be HOW or WHERE. The values are: - nil: add to the front - `set': replace the entire current value - other non-nil: append to the rear Also, a better value than `set' for the replacement function would be `replace'. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: SPC no longer completes when minibuffer-completing-file-name is t
Emacs now inserts a space when trying to complete an MH-E folder (for example, when visiting a folder or refiling a message). Could this change be responsible? 2005-12-06 Stefan Monnier [EMAIL PROTECTED] * minibuf.c (keys_of_minibuf): Just unbind SPC in Vminibuffer_local_filename_completion_map rather than forcing it explicitly to the same binding as the global map. BTW, shouldn't exactly the same change be made also for `Vminibuffer_local_must_match_filename_map'? -- Juri Linkov http://www.jurta.org/emacs/ ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: completion in find-file
I thought that the node (info (elisp)Reading File Names)
is more suitable place to document filename completion maps
than (info (elisp)Completion Commands).
Yes, that does seem better. Would you please move those @defvars?
I now think your original change was better because the node
Completion Commands is the place for all completion-related
variables. What is missing is a xref from Reading File Names to
Completion Commands pointing to filename completion maps active when
reading filenames. The patch below adds references that are similar how
normal keymaps are referenced from the documentation of completing-read.
Index: lispref/minibuf.texi
===
RCS file: /cvsroot/emacs/emacs/lispref/minibuf.texi,v
retrieving revision 1.69
diff -c -r1.69 minibuf.texi
*** lispref/minibuf.texi9 Dec 2005 04:38:40 - 1.69
--- lispref/minibuf.texi10 Dec 2005 01:04:36 -
***
*** 1023,1034
@defvar minibuffer-local-filename-completion-map
This is like @code{minibuffer-local-completion-map}
! except that it does not bind @key{SPC}.
@end defvar
@defvar minibuffer-local-must-match-filename-map
This is like @code{minibuffer-local-must-match-map}
! except that it does not bind @key{SPC}.
@end defvar
@node High-Level Completion
--- 1023,1036
@defvar minibuffer-local-filename-completion-map
This is like @code{minibuffer-local-completion-map}
! except that it does not bind @key{SPC}. This keymap is used by the
! function @code{read-file-name}.
@end defvar
@defvar minibuffer-local-must-match-filename-map
This is like @code{minibuffer-local-must-match-map}
! except that it does not bind @key{SPC}. This keymap is used by the
! function @code{read-file-name}.
@end defvar
@node High-Level Completion
***
*** 1212,1217
--- 1214,1225
@var{existing} is @code{nil}, then the name of a nonexistent file is
acceptable.
+ The function @code{read-file-name} uses
+ @code{minibuffer-local-filename-completion-map} as the keymap if
+ @var{existing} is @code{nil}, and uses
+ @code{minibuffer-local-must-match-filename-map} if @var{existing} is
+ [EMAIL PROTECTED] @xref{Completion Commands}.
+
The argument @var{directory} specifies the directory to use for
completion of relative file names. It should be an absolute directory
name. If @code{insert-default-directory} is [EMAIL PROTECTED],
--
Juri Linkov
http://www.jurta.org/emacs/
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Menu item for delete-selection-mode (was: DEL key doesn't kill mouse-dragged region)
Why not just turn on delete-selection-mode and transient-mark-mode, by default? transient-mark-mode is currently disabled by default, and has a menu item to easily enable it. delete-selection-mode is disabled too, but has no menu item to enable it. What about adding it to the Option menu? delete-selection-mode is no less useful than transient-mark-mode, especially for beginners. The menu item for transient-mark-mode is named Active Region Highlighting. What would be a good menu name for delete-selection-mode? -- Juri Linkov http://www.jurta.org/emacs/ ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: Menu item for delete-selection-mode (was: DEL key doesn't kill mouse-dragged region)
transient-mark-mode is currently disabled by default, and has a menu item to easily enable it. delete-selection-mode is disabled too, but has no menu item to enable it. What about adding it to the Option menu? delete-selection-mode is no less useful than transient-mark-mode, especially for beginners. The menu item for transient-mark-mode is named Active Region Highlighting. What would be a good menu name for delete-selection-mode? 1. Active Region Highlighting would be clearer as simply Highlight Selection or Highlight Active Selection. It is generally better to use verb phrases for menu items, and that is especially helpful for toggles, IMO. There is currently a mixture of verb phrases (e.g. Enter Debugger on Error) and noun phrases (e.g. Active Region Highlighting). Using verb phrases for all Options menu items would mean changing: - Syntax Highlighting to Highlight Syntactically or Highlight Syntax - Paren Match Highlighting to Highlight Matching Parentheses or Highlight Parentheses - Word Wrap in Text Modes to Wrap Words in Text Modes - Case-Insensitive Search to Search Case Insensitively or (if toggle were flipped) Search Case Sensitively - C-x/C-c/C-v Cut and Paste (CUA) to Use C-x, C-c, C-v to Cut, Copy, Paste - Automatic File De/compression to (De)Compress Files Automatically - Blinking Cursor to Let Cursor Blink or Blink Cursor The submenus correctly use verb phrases already, for the most part. 2. Type Over Selection, Overwrite Selection, or Overwrite Active Selection might be OK for delete-selection-mode. 3. If we generally use region in menus instead of selection, then the above would become Highlight Active Region and Overwrite Active Region (or Highlight Region and Overwrite Region). ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
