RE: Entering filenames with spaces

Could someone please tell me how this differentiation would best be implemented? Does a filename-minibuffer have an extra keymap? Or should Space be bound to some function that distinguishes the filename case from others? (a little awkward...) I use this to distinguish file-nam

RE: Saving minibuffer history

> Uh, Emacs 20? Why would one need to be compatible with that? > Many, many people do use Emacs 20, for a variety of reasons. Please remove emacs-devel from the Cc when discussing such issues. Why? This was the gist of my reply: If nothing is gained by breaking backward compati

RE: Yet another emacs icons

I think all of your icons are very pretty, but I liked the earlier "notebook" versions much better What do you mean by "notebook versions"? I can't match that with anything I remember seeing. Lennart has put all of the icons here: http://ourcomments.org/Emacs/NewIcons.htm

RE: Saving minibuffer history

Uh, Emacs 20? Why would one need to be compatible with that? Many, many people do use Emacs 20, for a variety of reasons. Emacs development does not have as a goal to be backward compatible - I understand that. I never said that Emacs 22 "needs" to be compatible with Emacs 20. If, however,

RE: Yet another emacs icons

_any_ of these new icons is better than the old Gnu/mushroom icon ... it looks basically like a piece of lint! The original image is far too detailed to ever be very useful as an icon Most of us agree (I think), that neither complex images nor text work well at icon size. I've already

RE: Saving minibuffer history

An improved version is now available at . FYI - I had some problems trying to use this library with Emacs 20, but if a few minor changes are made, it works well. Here are the problems I ran into: 1. (defcustom savehist-modes #o600 The rea

RE: wrapper fn for message and minibuffer-message?

> OK, I understand you now, I think. `message' does this: > > if `minibufferp', >then if `minibuffer-message-at-end' > then don't erase minibuffer, but append message there > else temporarily replace minibuffer contents with message >else temporar

RE: Qs on key-description, substitute-command-keys

> Does anyone know how to control which of several bindings for > a command is displayed by `substitute-command-keys'? There is no way to get this kind of control. I think we should devise some way to get the desired result without going through contorsions like `advertized-bl

RE: Qs on key-description, substitute-command-keys

> Does anyone know how to control which of several bindings for > a command is displayed by `substitute-command-keys'? There is the same problem for the key suggestion feature activated by `suggest-key-bindings' displaying in the echo area only the "first" key binding which is

RE: Saving minibuffer history

I've now improved this file somewhat (I wrote it eight years ago, and it shows). The new version is available at: http://fly.srk.fer.hr/~hniksic/emacs/savehist.el But the previous version didn't give me this byte-compile error (in Emacs 20): !! Invalid read syntax (("#"))

RE: Qs on key-description, substitute-command-keys

I never got any feedback on this question: Also, is there a good way to control which of several key bindings for a command is output by `substitute-command-keys'? The only way I've found is to make sure that the one I want is the last of the key sequences for that command defined

RE: Dedicated *Completions* frame iconified but not de-iconified

I recently started to show the *Completions* buffer in a dedicated frame: (setq same-window-buffer-names (remove "*Completions*" same-window-buffer-names)) (add-to-list 'special-display-buffer-names '("*Completions*" ((height . 20 After clicking on a

RE: wrapper fn for message and minibuffer-message?

`minibuffer-message-at-end' would have no effect when the minibuffer is not active. OK, I understand you now, I think. `message' does this: if `minibufferp', then if `minibuffer-message-at-end' then don't erase minibuffer, but append message there else temporari

RE: Better default values for tooltip padding and `tooltip-hide-delay'?

So it shouldn't be 0.75 as that is too small with 9x15. What about 0.8? It is reasonable with both fonts I tried, although the effect is less pronounced with the `default' font on Ubuntu. What do others think? Since you asked - I haven't tried any of the different fon

RE: wrapper fn for message and minibuffer-message?

I still have the same question: Would the variable also be set to non-nil implicitly, whenever `minibufferp'? (That was the behavior I originally suggested: use `minibuffer-message' when the minibuffer is active.) That is certainly not what I have in mind. Thes

RE: wrapper fn for message and minibuffer-message?

differences between `message' and `minibuffer-message': - `message' exits the minibuffer (and recursive edit); No it doesn't. My bad. - `minibuffer-message' wraps the message in " [...]"; `message' does not That's just a matter of how to make it sta

RE: wrapper fn for message and minibuffer-message?

I'd even argue that this function should be called "minibuffer-message", since currently minibuffer-message is only used when (minibufferp) is non-nil. I agree that is a natural generalization. But I agree that this name is not very clear for the current be

RE: Qs on key-description, substitute-command-keys

> to get the simpler representation, S-tab, from > the less readable ? if you want a Shift-TAB, try (kbd "S-TAB"), [(shift ?\t)], or [?\S-\C-i]. Thanks! Using [(shift ?\t)] works fine. ___ Emacs-devel mailing list Emacs-devel@gnu

RE: wrapper fn for message and minibuffer-message?

> (defun msg-maybe-in-minibuffer (string &rest args) > "Display STRING with `message' or `minibuffer-message', as appropriate." > (if (active-minibuffer-window) > (minibuffer-message (format " [%s]" string)) > (message string))) I agree 100% with the inte

Qs on key-description, substitute-command-keys

Why was the output from `key-description' and `substitute-command-keys' changed to use angle brackets around simple key sequences like S-tab? I have, for instance, a help string that looks like this when displayed: (S-tab or TAB: list, C-h: help). I mean, that's what it looks like in Emacs 20 - in

wrapper fn for message and minibuffer-message?

Ignore if already discussed or idea seems useless. I have some commands that users can use either at top level or when in the minibuffer. (In the latter case, they are bound to keys.) I use the following wrapper function, and I wonder if such a function might not be useful generally, for defining

RE: Minibuffer bindings.

I was wondering why C-p and C-n are not binded like and in the minibuffer. I agree. In fact, as I wrote on 9/01 (RE: make `occur' use word at point as default), I was thinking this was already the case (RMS corrected me). Although my main point was that we could redefine some of

RE: Cannot use "\C-!" in a string in Emacs 22?

> (define-key my-map "\C-!" 'my-cmd), which works in Emacs 20, but > gives this error in Emacs 22: "Invalid modifier in string". It worked under Emacs-20, but returned the same as "\C-a" Thanks. In Emacs-21 this was fixed to return an error > I settled on (define-key

Cannot use "\C-!" in a string in Emacs 22?

I'm interested in a key-binding syntax that works with Emacs 20 through 22 (for those bindings that are acceptable to all of those versions). The (kbd ...) syntax, for instance, doesn't work with earlier Emacsen, so that choice is out, for me. I tried (define-key my-map "\C-!" 'my-cmd), which work

RE: Argument names in Elisp Reference vs docstrings

[completions] doesn't quite fit for an alist, an obarray, or a hash table, or a function to test them. Unfortunately, `collection' does best. `completions' fails utterly. Moreover, is not the focus on the whole group, not on its individual elements, members, or items?

RE: Argument names in Elisp Reference vs docstrings

> I don't like "collection" very much. "collection" is used in the Emacs Lisp Reference Manual for the functions `try-completion', `all-completions', `test-completion' and `completing-read'. `collection' is the best name I could think of for this purpose, b

RE: Argument names in Elisp Reference vs docstrings

> I didn't realize this was already decided. Are these default values > accessed via repeated M-n? Yes, very much like values from the history list are accessed via repeated M-p. I followed the discussion; I just didn't realize a decision had been made. > My point was that "i

RE: Argument names in Elisp Reference vs docstrings

> I think it hasn't been decided whether to allow more than one default value > in the upcoming release. IIUC, Richard decided to allow more than one default value, since this is a quite trivial change. I didn't realize this was already decided. Are these default values access

RE: Argument names in Elisp Reference vs docstrings

I propose to standardize on the following arguments names: prompt initial history defaults inherit-im must-match collection no-space directory Most of these names are shorter than current names, but still intelligible. Since `d

RE: Bindings on the mode-line

I support this proposal. Emacs doesn't have convention for the usage of mouse-[1-3]. It is good time to define a convention like C-x for global binding prefix and C-c for major mode prefix. I don't know if this is a good time for that - I doubt it. It will likely be another wrestling m

RE: quitting help buffer

I don't want `q' to iconify the frame, slip it in my back pocket, mail it to me, or do any of the other strange and wonderful things I see advertised in the doc for `view-mode'. How can I get `q' to do something as simple as kill the buffer an

RE: Patch: Follow convention for reading with the minibuffer.

I guess the current format of the default buffer prompt was easier to implement. Finding an appropriate place in the given prompt to insert the default value is not a trivial task to do in C. This suggests a simple solution: define a convention whereby the prompt s

quitting help buffer

I cannot figure out how to make `q' do what it used to do in Emacs 20, to quit the *Help* buffer. I use non-nil `pop-up-frames'. I want `q' to do the equivalent of `quit-window'. In my context, that will kill the buffer and delete its frame (thanks to my redefining `delete-window' to DTRT for one-

RE: where-is-internal question

> (define-key some-map [remap self-insert-command] 'my-command) > What is a good way to "undo" this remapping? (define-key some-map [remap self-insert-command] nil) Thanks. ___ Emacs-devel mailing list Emacs-devel@gnu.org http://list

RE: where-is-internal question

(define-key some-map [remap self-insert-command] 'my-command) This really should be for help-gnu-emacs, but, since you've already been so helpful... What is a good way to "undo" this remapping? Looking at the doc (info), it looks as if I cannot then do this: (define-key some-map [remap m

RE: where-is-internal question

> (dolist (key (where-is-internal 'self-insert-command > global-map)) > (define-key my-map key 'my-command))) Also the above dolist is advantageously replaced by a call to substitute-key-definition Of

RE: where-is-internal question

(if (boundp 'this-original-command) (define-key my-map [remap self-insert-command] 'my-command) (dolist (key (where-is-internal 'self-insert-command global-map)) (define-key my-map key 'my-comman

RE: make `occur' use word at point as default

But I think it would be more convenient to [use M-n to] add [additional default values] to the list for [M-p] to access. We seem to be miscommunicating; your additions turn this into something very different from what I was talking about. Sorry; I tried. Could you

RE: where-is-internal question

In previous Emacs versions, I could do this, to bind stuff that is bound to self-insert-command in the global map: (dolist (key (where-is-internal 'self-insert-command global-map)) (define-key my-map key 'my-command)) Now, however, it looks like I need to do something like

where-is-internal question

I haven't looked into this in detail - forgive my incomplete understanding. I'm looking for help on where-is-internal - as regards command remapping (I guess). In previous Emacs versions, I could do this, to bind stuff that is bound to self-insert-command in the global map: (dolist (key (where-i

RE: key-binding values

> Is this as good as can be expected - is there no way to get something more > readable for [?\C-\ ]? (key-description [67108896]) => "C-SPC" (key-description "\C- ") => "C-@" Yes, that's what key-description is for. My question was, "is this as good as can be expected from C-

key-binding values

Consider these two definitions: (defcustom my-key [?\C-\ ] "My key sequence.") (defcustom my-key "\C- " "My key sequence.") `C-h v' then gives these values: [67108896] and "^@". Is this as good as can be expected - is there no way to get something more readable for [?\C-\ ]? Emacs users lear

RE: make `occur' use word at point as default

NEXT could conceivably be used to access another default. It's a good idea to reserve [next] for a complementary use with [prior] - that's a natural pair, and such pairs are relatively scarce. What's more, their names are perfect for forward-backward operations that do what they say. FWIW

RE: make `occur' use word at point as default

C-n and C-p ... do the usual cursor motion [in the minibuffer] I replied: You're right. My bad. I should have added that I doubt that such up and down cursor motions are very useful in the minibuffer. ___ Emacs-devel mailing list

RE: make `occur' use word at point as default

There is currently a good deal of redundancy in the bindings for `next-history-element' and `previous-history-element'. These minibuffer history-list commands are bound to *FOUR PAIRS* of keys: (1) arrows [up] / [down], (2) C-n / C-p, (3) M-n / M-p, and (4) [

RE: make `occur' use word at point as default

> Could none of those history-list bindings be sacrificed for accessing > "default" values (such as those Juri & Stefan have mentioned, > and/or the values in `minibuffer-completion-table')? There are two different issues here: accessing the completion values, and accessing the

RE: make `occur' use word at point as default

However, you might consider giving access to a list of "default values" (more than just 1 or 2) via _different_ keys from M-n and M-p - the arrow keys, for instance. Finding other keys would be difficult. Why? There is currently a good deal of redundancy in the binding

RE: make `occur' use word at point as default

> 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 access

should doc on case-fold-search mention that there are other such vars also?

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

RE: make `occur' use word at point as default

> The command `occur' currently uses the last item in the regexp > history as the default value. > Please do not change that. Peopel are accustomed to just typing RET > to search for the same thing again. That's a good point. But the problem remains: too often I ha

RE: patch for woman (woman-topic-at-point)

> is there a more elegant way of writing the following? >(and word-at-point >(test-completion word-at-point woman-topic-all-completions) >word-at-point) (when (and word-at-point (test-completion word-at-point woman-topic-all-completions))

RE: Emacs icons

Attached you will find two more ideas for an Emacs icon ;-) The E can be seen. I don't see anything bad about this, but since I am not an expert on icons, I wonder what others think. The E can be seen. IMO, it would be better alone, larger, and with more contrast against the back

RE: "What's This?" in Describe submenu

Resending, as I don't think this got through, for some reason. Apologies if you already received this. Sent: Monday, August 22, 2005 9:24 AM What is the purpose of the "What's This?" entry in the Describe submenu of the Help menu? The only difference to the "Describe Key.

RE: "What's This?" in Describe submenu

In its current form, it does IN NO WAY resemble what a Windoze user would expect from the "What's this" function. When you click on the "What's this" function in Windoze (typically not available as a menu item, but as a [?] icon), the cursor changes shape to an arrow with a que

RE: "What's This?" in Describe submenu

What is the purpose of the "What's This?" entry in the Describe submenu of the Help menu? The only difference to the "Describe Key..." entry beneath is that the latter is bound to `describe-key-1' which is not defined anywhere. (RMS:) A discussion in November 2

RE: Emacs icons

What a coincidence! I threw out that E = macs idea, independently, a week ago. I guess it must be a fairly obvious thing to "discover", but, even so, I'm still a bit surprised. I'm sure I never saw this anywhere. - Drew >> (in allusion to Einstein's E=mc2)? Could look nice with colors and

RE: Avoiding moving point into minibuffer prompt area

- Neither the Emacs manual nor the Emacs-Lisp manual contains the word "inviolable". I think I will change it to "don't enter". Simple and clear. Thanks. ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.g

RE: update of emacsclient.1

Under "DESCRIPTION" it says: You typically do not call emacsclient directly. Instead, you set the environment variable EDITOR to emacsclient and let programs like 'vipw' or 'bug' or anything run it for you, which will use an existing Emacs to visit the file.

RE: Avoiding moving point into minibuffer prompt area

I'd still be interested in knowing what your text-copying use case is. I sometimes use command history to turn an interactive command into a piece of lisp code to use later, or at least study how it was invoked, or reinvoke it on a variable instead of a literal string. Sor

RE: Avoiding moving point into minibuffer prompt area

On a related subject, and being a bit nit-picky - does anyone else think that these things should be harmonized & better documented? - Neither the Emacs manual nor the Emacs-Lisp manual contains the word "inviolable". - Both manuals refer to the "intangible" property. - Is "intangible" not th

RE: Avoiding moving point into minibuffer prompt area

Well, now that I'm clear on the rest of the thread, I realize I'm talking about a different part. No, I've never moved dot into the prompt. OK. Thanks for clearing it up. ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.g

RE: Emacs icons

Here is one crack, the 48x48 version and a 16x16 version. BTW if anyone want to play with this some of the Gimp xcf files are at the same directory as the images for the web page. The logo is OK, as a logo (like the Nike swoosh). If it became known to everyone _as a logo_, then it coul

RE: Avoiding moving point into minibuffer prompt area

One possible compromise, assuming there is a useful use case for copying prompt text, would be to permit copying it with the mouse, but still inhibit moving the cursor into the prompt by command or keyboard. Would that be good enough? That would force one to use th

RE: Avoiding moving point into minibuffer prompt area

As I already pointed out, I personally do not find this confusing, but very useful. For people who do not like it, however, the functionality you want is already available. M-x customize-option RET minibuffer-prompt-properties RET and check: Inviolable. Thanks. I wasn't aware

RE: Avoiding moving point into minibuffer prompt area

I think it is quite confusing that you can move the point into the prompt area in the minibuffer. What is confusing about that? It has often saved me time by allowing me to copy text from the minibuffer. The code you propose would unnecessarily waste people's time by im

RE: Emacs icons

> The idea of using an E on a gnu is ok semantically. Whether it looks > better than just an E, I am not sure. Attached is an idea ;-) It don't look too bad when resized as a 16x16 icon. This could make an attractive _logo_, but it would _not_ work as a 16x16 icon, IMO (see attached)

RE: Entering filenames with spaces

> There is lots that is unexpected or new in Emacs, and much of it is > desirable because it optimizes ease of use - IOW, some Emacs UI > features are new to people, but they are good. It is better to help > new users to learn the Emacs way of doing things, _if it is better_, >

RE: Emacs icons (was: Suggestions for the temporary windowsusedfrom the minibuffer)

- The best symbol for Emacs is plain, typewriter-font _text_. A single letter is good as a representation of a text editor (no flames about how Emacs is so much more). "E" for Emacs is good, clear, and recognizable. Just an E is an idea worth trying.

RE: Entering filenames with spaces

>For those who want to use something besides SPC for word completion, a good >candidate is a left-hand key that is normally a prefix key, and that doesn't >have much use in the minibuffer - a key such as C-SPC or C-z C-z is a CUA key for undo and as such is it used in every w32 pro

RE: Entering filenames with spaces

> The point is that users are free to get rid of the SPC bindings to > minibuffer-complete-word. I think that David was saying that he > never uses word completion - in that case, just removing the > bindings suffices. Those who do use it have several options, > including the al

RE: Entering filenames with spaces

> This gives you the convenience of using the spacebar for word > completion, a > more convenient way to insert a space (`C-SPC' is almost as > convenient as `SPC'), and lets you change things easily if you like. Note that C-SPC (which is often the same as C-@ on text terminals

RE: Entering filenames with spaces

David> IIRC, people seemed to agree and some said that they wouldn't David> use minibuffer- complete-word anyways - especially for David> filenames it seems to be clear that minibuffer-complete-word David> makes no sense. Inputting a space in a file name, however, is David> a p

RE: Suggestions for the temporary windows used from the minibuffer

> 1) Add help to the isearch prompt > > I am not sure whether that is a good idea. > I think we should poll the users about it. What is meant by #1 - what is the "isearch prompt", and how would help be added to it? If you mean just "let C-s C-h display isearch-mode-help", then

RE: Emacs icons (was: Suggestions for the temporary windows usedfrom the minibuffer)

s Or E = m c (for relativity fans) a It is a nice idea, but can that much be expressed clearly in so few pixels? I think probably not. No, surely not. I was partly kidding. My serious 2 cents: - Understandability and recognizabi

RE: Leaving isearch-mode and keeping the highlite

>Turning it on by a particular exit key sequence is not the >best way. I would >rather have that be a user option (like case-fold-search), and >be able to >toggle the option while in isearch (like we can toggle >case-fold-search). Too cumbersome to me. Sometimes I want

RE: Leaving isearch-mode and keeping the highlite

I would find it very helpful to be able to leave isearch-mode but keep the highlite put it on C-RET or S-RET in isearch-mode-map. Could be useful. The main question is how to later get rid of it. Perhaps the next isearch could do that, or let isearch toggle it (see below). Turning it

Emacs icons (was: Suggestions for the temporary windows used from the minibuffer)

I'd rather go the line of what makes Emacs a special editor. Something like a Gnu had floating above some typical key combinations like "C-c M-x C-M-\" or one could go for the lisp, e.g. by a Gnu head enclosed in two big parentheses. Why not just text? No sinks, antelopes or geneti

RE: Todays exercise of sanity (or does "see" really match "not"?)

You shouldn't search with the `s' command, except as the last resort. You should search with the `i' command, which does not have this deficiency. That helps me find many (but not all) occurrences of "menu". Thanks. It would still be useful to fix the deficiency in `s' search, however

RE: Todays exercise of sanity (or does "see" really match "not"?)

Just a reminder, I guess, with another example of why this should eventually be fixed. I'm coming back to this thread from 2005/03/21. I think we all agreed to worry about this later, and that 1) programs should somehow be able to search for and see metadata (such as Note: and Menu: tags), but tha

RE: Suggestions for the temporary windows used from the minibuffer

For keys that are bound to commands that manipulate the "other" window, bind them instead to commands that do the same thing when there is another window, but let the user do something else, otherwise? The basic idea that these keys could do something else as a

RE: Suggestions for the temporary windows used from the minibuffer

On a slightly related subject - Commands scroll-other-window and scroll-other-window-down manipulate the "other" window, if it exists. If it doesn't, they do nothing. That makes sense for the commands, but not for the keys they are bound to. Keys are limited, and handy pairs of keys like (, ) and

RE: set-frame-position - is it a bug?

the intention of the following code (setq fpx (cdr (assoc 'left (frame-parameters (setq fpy (cdr (assoc 'top (frame-parameters (setq fpx (+ 1 fpx)) (set-frame-position (next-frame) fpx fpy) is to move the frame honizontally 1 pixel right; but as a side-e

RE: set-frame-position - is it a bug?

>From Pascal Bourguignon: IMO it's a bug in the interaction between emacs and the window manager. With my version of emacs "22.0.50.1", and with my window manager (WindowMaker), it works In my version of 22.0.50.1 and window manager (Windows XP), it's broken: In GNU Emacs 22.0.50.1 (i

set-* frame parameter functions (e.g. set-foreground-color)

There is a general set-frame-parameter function. There are also specific functions like set-foreground-color. The specific functions don't accept a frame argument. Why not let the specific functions also accept an optional frame argument? This would be slightly more readable: (set-foreground-color

RE: [EMAIL PROTECTED]: Info on define-minor-mode -:init-valueor :initial-value?]

What if I just document in the Elisp manual what the acceptable situations are for a non-nil :init-value and how it needs to be handled: pre-load the file containing the define-minor-mode before startup.el and call the minor mode function (or custom-reevaluate-setting if the

RE: [EMAIL PROTECTED]: Info on define-minor-mode - :init-valueor :initial-value?]

> (if foo-mode (foo-mode 1)) This will turn on the minor mode if you happen to browse the corresponding customize group (because Custom will then load the file). I.e. it'd be a bug. Sorry, I don't understand. If the variable is t, then the mode should be turned on, no? Does i

RE: [EMAIL PROTECTED]: Info on define-minor-mode - :init-valueor :initial-value?]

For the moment, I just replaced the incorrect keyword :initial-value in the example with :init-value. Thanks. > There is more. You can not specify a non-nil :init-value, unless > either the minor mode is enabled by just setting the variable or > unless you do something

RE: completing-read prompt - faces?

so completing-read would respect the string's properties - at least the face property? You could bind minibuffer-prompt-properties not to include the face property. Thanks; I wasn't aware of that variable. BTW, what's a good way to remove a property and its value from a p

RE: completing-read (and M-x) with pop-up-framesnon-nilchangesframefocus

il? Stefan's patch (untested on Windows): -Original Message- From: Stefan Monnier [mailto:[EMAIL PROTECTED] Sent: Friday, July 15, 2005 12:36 AM To: Drew Adams Cc: Emacs-Devel Subject: Re: completing-read (and M-x) with pop-up-frames non-nil changes fra

RE: completing-read (and M-x) with pop-up-frames non-nilchangesframefocus

When focus follows the mouse, it is difficult to avoid selecting it if it shows up under the mouse. I didn't have focus-follows-mouse turned on. If it were on, and if the new frame did not happen to show up under the mouse, it would not be selected, right?

completing-read prompt - faces?

It looks as if any properties (e.g. face) belonging to the prompt string you pass to completing-read are ignored. This would, I guess, be a new feature request, but is there any chance to change this soon, so completing-read would respect the string's properties - at least the face property? Likew

RE: completing-read (and M-x) with pop-up-frames non-nil changesframefocus

On Windows, you have to manually select original the frame (e.g. click the title bar). In any case, you should not need to move the mouse or click the original frame. *Completions* should only be displayed, not selected, whether or not it is in anoth

RE: completing-read (and M-x) with pop-up-frames non-nil changes framefocus

This opens a new frame for buffer *Completions*. At least in Windows, the new frame is selected. The frame focus for typing key sequences thus switches to the *Completions* frame, but the minibuffer of the original frame is still waiting for input. So

RE: Better default values for tooltip padding and `tooltip-hide-delay'?

1. the `padding' of the tooltips too large. ... 2. `tooltip-hide-delay' defaults to 10 seconds. IMO, this is far too long. FWIW, I agree with both points. ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailm

RE: completing-read (and M-x) with pop-up-frames non-nil changes frame focus

I'm far from sure it'll fix the bug and if it doesn't, I'd rather not install it, so please have someone try it before I install it, I agree, but I don't have a way to check it myself. ___ Emacs-devel mailing list Emacs-devel@gnu.org http

RE: completing-read (and M-x) with pop-up-frames non-nil changes frame focus

> emacs -q > M-x set-variable pop-up-frames t > M-x complet TAB > This opens a new frame for buffer *Completions*. At least in Windows, the > new frame is selected. The frame focus for typing key sequences thus > switches to the *Completions* frame, but the minibuffer o

completing-read (and M-x) with pop-up-frames non-nil changes frame focus

emacs -q M-x set-variable pop-up-frames t M-x complet TAB This opens a new frame for buffer *Completions*. At least in Windows, the new frame is selected. The frame focus for typing key sequences thus switches to the *Completions* frame, but the minibuffer of the original frame is still waiting fo

RE: [h-e-w] Re: Patch to fix frame positioning with negative top/leftvalues on Windows

> I should have said what the symptom of the malfunction is that, on > Windows, when you evaluate this Elisp code: > > (make-frame '((top . -1) (left . -1))) > > the new frame will not be positioned with its bottom-right corner in the > bottom-right of the display.

RE: obsolete comment in tool-bar.el

(defvar rogue-var) ;; to silence the compiler for the next line. (unless (default-boundp rogue-var) (setq rogue-var nil)) (defcustom rogue-var ... ... :initialize 'custom-initialize-set ...) Suppose we implement a keyword in defcustom that caus

RE: Sorting of directories in dired

> IOW, aside from putting directories first and not being case-sensitive, the > Windows listing also throws out the uid and gid, which don't mean a lot for > Windows. They might not mean a lot now, but that's only because no one bothered to write the code to use the Win

  1   2   3   >