> The original message said:
>
>However I might just want to select that window to resize it
>
> so AFAICT this whole thread has been about a confusion between "click
> mouse-1 to follow link" and "click mouse-1 to give focus to a *frame*".
>
> Of course maybe he really meant "window
Stefan Monnier <[EMAIL PROTECTED]> writes:
> Of course maybe he really meant "window", but that seems rather unlikely
> to me. This said, I agree that I'd have expected the window-manager to take
> care of such things (basically the window-manager shouldn't pass on
> a mouse-1 click to the applic
>> > IIRC, you were the one to propose _not_ following a link in a
>> > non-selected window, and I initially said it made sense (so I
>> > implemented it unconditionally).
>>
>> I meant "frame", sorry.
> Am I seriously misunderstanding something? Is not the Emacs window focus
> what a user is int
- Original Message -
From: "Stefan Monnier" <[EMAIL PROTECTED]>
> > IIRC, you were the one to propose _not_ following a link in a
> > non-selected window, and I initially said it made sense (so I
> > implemented it unconditionally).
>
> I meant "frame", sorry.
Am I seriously misunderstan
> IIRC, you were the one to propose _not_ following a link in a
> non-selected window, and I initially said it made sense (so I
> implemented it unconditionally).
I meant "frame", sorry.
Stefan
___
Emacs-devel mailing list
Emacs-devel@gnu.org
a) a double-click on a location that has no double-click binding, but
a local mouse-2 binding, will execute the mouse-2 binding. This
will make double-clicks, where not overriden, follow links without
further code changes compared to 21.4
This means two different modes of
David Kastrup <[EMAIL PROTECTED]> writes:
> Richard Stallman <[EMAIL PROTECTED]> writes:
>
>> In order not to confuse people too much, I really would want to
>> suggest strongly that we remap double-click to mouse-2 unconditionally
>> by default (where a "stronger" mouse-2 binding exis
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> I have added a new option mouse-1-click-in-non-selected-windows
>> that controls whether mouse-1 click in non-selected windows
>> will follow links. Default is t.
>
> I think it should be purely and simply removed.
> It addresses the "click to focus w
On Fri, Feb 25 2005, David Kastrup wrote:
> I would recommend not making any behavior by default dependent on the
> single-click length, nor on the focus situation: both approaches are
> completely obfuscate and confusing.
>
> So the change to 21.4 behavior would be the following:
>
> a) a double-
>>> I have added a new option mouse-1-click-in-non-selected-windows
>>> that controls whether mouse-1 click in non-selected windows
>>> will follow links. Default is t.
>>
>> I think it should be purely and simply removed.
>> It addresses the "click to focus window" problem but nobody ever compla
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> I have added a new option mouse-1-click-in-non-selected-windows
>> that controls whether mouse-1 click in non-selected windows
>> will follow links. Default is t.
>
> I think it should be purely and simply removed.
> It addresses the "click to focus w
> I have added a new option mouse-1-click-in-non-selected-windows
> that controls whether mouse-1 click in non-selected windows
> will follow links. Default is t.
I think it should be purely and simply removed.
It addresses the "click to focus window" problem but nobody ever complained
about it (
> Bad generalization. A better generalization is "Whenever David
> discusses something, he screams like Howard Dean in Iowa." But
> neither generalization is very good.
Whatever. Enough people have pointed out by now that they see little
merit or sense or consistency or logic
"Drew Adams" <[EMAIL PROTECTED]> writes:
> > I use mouse-1 to set point currently, as usual (no
> > double-clicking). If we changed mouse-1 to follow links, then I
> > would double-click to set point - or I would forego
> > mouse-1-follows-links. "Simple editing" would not be affec
Richard Stallman <[EMAIL PROTECTED]> writes:
> In order not to confuse people too much, I really would want to
> suggest strongly that we remap double-click to mouse-2 unconditionally
> by default (where a "stronger" mouse-2 binding exists), and also map
> mouse-1 to the same when
> I use mouse-1 to set point currently, as usual (no
> double-clicking). If we changed mouse-1 to follow links, then I
> would double-click to set point - or I would forego
> mouse-1-follows-links. "Simple editing" would not be affected
> detrimentally by what I or Kim described
[EMAIL PROTECTED] (Kim F. Storm) writes:
>> I am afraid that the same is the case here. I have
>> focus-follows-mouse set here by default in the window manager, so I
>> don't expect clicks that don't do anything. The current behavior
>> (where a window change does not follow links at all) is mor
- Original Message -
From: "David Kastrup" <[EMAIL PROTECTED]>
> > AFAICT the specific problem at hand is that a mous-1 click used to
> > get focus should not follow a link. No matter what kind of link, no
> > matter the major mode.
>
> That's not the only problem. A mouse-1 click not u
In order not to confuse people too much, I really would want to
suggest strongly that we remap double-click to mouse-2 unconditionally
by default (where a "stronger" mouse-2 binding exists), and also map
mouse-1 to the same when the special "link" property is present.
I do not see
No. I wasn't aware of that. With the default setting, the user would have to
move the mouse and release it within 350 milliseconds for it to have any
effect. I think must be quite hard to do.
I don't think that is what it does--is there perhaps a misunderstanding?
__
... intuitive
`Intuitive' is the wrong word. When I started with a windowing
system, my mnemonic was `m means menue'. That is because the middle
mouse button on that system evoked a menu.
In this window, `m means mouse-yank-at-click'. This is different.
As for `set point', `set mark', `
> Terrible. If I tell that to any new Emacs users, they'll
> shake their heads and leave Emacs alone.
> And when you tell them about mouse-1 plus mouse-3 and all the rest?
The difference is that you don't need to tell Emacs novices about
mouse-1+mouse-3 (which I never
"Drew Adams" <[EMAIL PROTECTED]> writes:
> See above. I use mouse-1 to set point currently, as usual (no
> double-clicking). If we changed mouse-1 to follow links, then I
> would double-click to set point - or I would forego
> mouse-1-follows-links. "Simple editing" would not be affected
> detrime
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> Terrible. If I tell that to any new Emacs users, they'll shake
>> their heads and leave Emacs alone.
>
>> And when you tell them about mouse-1 plus mouse-3 and all the rest?
>
> The difference is that you don't need to tell Emacs novices about
> Terrible. If I tell that to any new Emacs users, they'll shake their
> heads and leave Emacs alone.
> And when you tell them about mouse-1 plus mouse-3 and all the rest?
The difference is that you don't need to tell Emacs novices about
mouse-1+mouse-3 (which I never ever use in Emacs,
> Just to add one more permutation to our list of contortions ;-) -
>
> I would like to see modes like Dired and Grep and Buffer List make
> the entire line, which is in fact the entire entry, clickable and
> mouse-highlightable, as I think I mentioned before.
For one thing
"Drew Adams" <[EMAIL PROTECTED]> writes:
> If we have specific problems in certain modes, let's fix those
> modes (e.g. in grep that you have to click on the file:line part
> of a line to jump).
>
> Just to add one more permutation to our list of contortions ;-) -
>
> I would like to s
>>> If we have specific problems in certain modes, let's fix those
>>> modes (e.g. in grep that you have to click on the file:line
>>> part of a line to jump).
>>
>> AFAICT the specific problem at hand is that a mous-1 click used to
>> get focus should not follow a link. No matter what kind of li
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> If we have specific problems in certain modes, let's fix those
>> modes (e.g. in grep that you have to click on the file:line
>> part of a line to jump).
>
> AFAICT the specific problem at hand is that a mous-1 click used to
> get focus should not foll
If we have specific problems in certain modes, let's fix those
modes (e.g. in grep that you have to click on the file:line
part of a line to jump).
Just to add one more permutation to our list of contortions ;-) -
I would like to see modes like Dired and Grep and Buffer List make the
> If we have specific problems in certain modes, let's fix those
> modes (e.g. in grep that you have to click on the file:line
> part of a line to jump).
AFAICT the specific problem at hand is that a mous-1 click used to get focus
should not follow a link. No matter what kind of link, no matter t
"Lennart Borgman" <[EMAIL PROTECTED]> writes:
> - Original Message -
> From: "Stefan Monnier" <[EMAIL PROTECTED]>
>
>> I vote to change mouse-1-click-follows-link to `double'.
>
>>From a usability point I do not like double-clicks. If most links are single
> click links (and they are in a
[EMAIL PROTECTED] (Kim F. Storm) writes:
> Stefan Monnier <[EMAIL PROTECTED]> writes:
>
>> I vote to change mouse-1-click-follows-link to `double'.
>
> The whole point of mouse-1-click-follows-link is to make emacs behave
> like most other (modern) applications.
>
> Double click to follow a link
Stefan Monnier <[EMAIL PROTECTED]> writes:
> I vote to change mouse-1-click-follows-link to `double'.
The whole point of mouse-1-click-follows-link is to make emacs behave
like most other (modern) applications.
Double click to follow a link is not modern!
If we have specific problems in certai
"Lennart Borgman" <[EMAIL PROTECTED]> writes:
> - Original Message -
> From: "Stefan Monnier" <[EMAIL PROTECTED]>
>
>> I vote to change mouse-1-click-follows-link to `double'.
>
>>From a usability point I do not like double-clicks. If most links are single
> click links (and they are in a
- Original Message -
From: "Stefan Monnier" <[EMAIL PROTECTED]>
> I vote to change mouse-1-click-follows-link to `double'.
>From a usability point I do not like double-clicks. If most links are single
click links (and they are in a web browser) I think we should as far as
possible use si
I vote to change mouse-1-click-follows-link to `double'.
Stefan
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
David Kastrup <[EMAIL PROTECTED]> writes:
>> My preferences remained unchanged but I also think it must be
>> confusing for a novice user. Before I was aware of the time limit, I
>> didn't understand why clicking mouse-1 sometimes popped to a new
>> buffer and other times didn't.
>
> I am afraid t
Nick Roberts <[EMAIL PROTECTED]> writes:
> > The grep buffer is an example. If I try to place the cursor anywhere on
> > a line before the end of a match, the associated file pops up in
> > another buffer. However I might just want to select that window to
> > resize it.
> >
> The grep buffer is an example. If I try to place the cursor anywhere on
> a line before the end of a match, the associated file pops up in
> another buffer. However I might just want to select that window to
> resize it.
>
> When you found this not to your taste, were you a
The grep buffer is an example. If I try to place the
cursor anywhere on a line before the end of a match, the associated file
pops up in another buffer. However I might just want to select that window
to resize it.
When you found this not to your taste, were you aware about the asp
I just installed a change so that a mouse-1 click only follows a link
if the window is already selected.
The tooltip will now say to use mouse-2 to follow a link in a
non-selected window and to use mouse-1 in a selected window.
I don't think it's a good idea to put the info about
Stefan Monnier <[EMAIL PROTECTED]> writes:
> Is that going to correctly "ignore" this last mouse-1 click other than make
> it change focus) because, from Emacs's point of view, the window Foo has
> always been and still is the selected window?
In any case, you can always use a "long click" or dra
Stefan Monnier <[EMAIL PROTECTED]> writes:
>>> I made the same suggestion as Stefan, and I don't think it would lead to
>>> further confusion. As I mentioned, that is pretty much the behavior that
>>> Windows users experience every day (the first click establishes focus). And
>
>> This makes sense
>> I made the same suggestion as Stefan, and I don't think it would lead to
>> further confusion. As I mentioned, that is pretty much the behavior that
>> Windows users experience every day (the first click establishes focus). And
> This makes sense!
> I just installed a change so that a mouse-1
"Drew Adams" <[EMAIL PROTECTED]> writes:
> > Based on your example, I'd say another option might be:
> > - if the click is used to give focus, then don't follow the link.
> I made the same suggestion as Stefan, and I don't think it would lead to
> further confusion. As I mentioned, that
Jason Rumney <[EMAIL PROTECTED]> writes:
> David Kastrup <[EMAIL PROTECTED]> writes:
>
>> I forgot: when we discussed the possible desirable behaviors, was
>> follow-link-on-double-click among it? Isn't that sort of common
>> for launching something? It would of course shadow marking a word
>> i
Nick Roberts <[EMAIL PROTECTED]> writes:
> Given that if you press the button longer it also doesn't follow the
> link, the tooltip tells you that it does, even without focus, and
> doesn't mention that mouse-2 does the job too (it's masked by
> mouse-1), I think it would only create further confu
David Kastrup <[EMAIL PROTECTED]> writes:
> I forgot: when we discussed the possible desirable behaviors, was
> follow-link-on-double-click among it? Isn't that sort of common for
> launching something? It would of course shadow marking a word in a
> link, but I guess that is less tragic than lo
> Based on your example, I'd say another option might be:
> - if the click is used to give focus, then don't follow the link.
Given that if you press the button longer it also doesn't
follow the link, the
tooltip tells you that it does, even without focus, and doesn't
men
This "double click to launch" used to be a pretty common idiom at one
time,
though browsers have watered it down in some contexts.
FWIW - I'm not an expert on this, but I believe that in Windows the single-
vs double-click-follows/activates behavior is a user option. I would guess
(but don
Luc Teirlinck <[EMAIL PROTECTED]> writes:
>I forgot: when we discussed the possible desirable behaviors, was
>follow-link-on-double-click among it?
>
> Sorry, in my previous reply I misread `double-click' for mouse-2.
> But yes there is such a value. You have to set it to 'double.
Actual
If value is an integer,...
If value is `double', a double click follows the link.
Otherwise, a single Mouse-1 click unconditionally follows the link.
Would "For any other non-nil value," not be clearer than "Otherwise,"
which seems to include _all_ other possibilities, including nil.
S
I forgot: when we discussed the possible desirable behaviors, was
follow-link-on-double-click among it?
Sorry, in my previous reply I misread `double-click' for mouse-2. But
yes there is such a value. You have to set it to 'double.
Sincerely,
Luc.
_
David Kastrup wrote:
I forgot: when we discussed the possible desirable behaviors, was
follow-link-on-double-click among it?
I believe that setting the option to nil does that.
That was, as I already said, the result of misreading `double-click'
for mouse-2. If you set it to n
I believe that the idea was to have the mouse-1 follow-links
(and activate buttons) behavior be a user option.
You mean `mouse-1-click-follows-link'? It _is_ a user option. I
personally have it set to nil. But the default value uses the new
behavior.
Yes, that's
> Based on your example, I'd say another option might be:
> - if the click is used to give focus, then don't follow the link.
Given that if you press the button longer it also doesn't follow the link, the
tooltip tells you that it does, even without focus, and doesn't mention that
mouse-2 does
Luc Teirlinck <[EMAIL PROTECTED]> writes:
> Drew Adams wrote:
>
>I believe that the idea was to have the mouse-1 follow-links (and activate
>buttons) behavior be a user option.
>
> You mean `mouse-1-click-follows-link'? It _is_ a user option. I
> personally have it set to nil. But the d
David Kastrup <[EMAIL PROTECTED]> writes:
> Press the button for longer. That avoids following the link. How to
> teach this best is a different question.
View at it like this:
Press the mouse button "harder" (i.e. longer)
to make it stick where you click.
Here's the releva
David Kastrup wrote:
I forgot: when we discussed the possible desirable behaviors, was
follow-link-on-double-click among it?
I believe that setting the option to nil does that.
Sincerely,
Luc.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
h
>I believe that the idea was to have the mouse-1 follow-links (and activate
>buttons) behavior be a user option.
>
> You mean `mouse-1-click-follows-link'? It _is_ a user option. I
> personally have it set to nil. But the default value uses the new
> behavior.
But I like it in I
Drew Adams wrote:
I believe that the idea was to have the mouse-1 follow-links (and activate
buttons) behavior be a user option.
You mean `mouse-1-click-follows-link'? It _is_ a user option. I
personally have it set to nil. But the default value uses the new
behavior.
Sincerely,
Luc.
- Original Message -
From: "Nick Roberts" <[EMAIL PROTECTED]>
> I realise that applications like web browsers use mouse-1 to follow links,
so
...
> be daunting for the new user, so I suggest the following:
>
> 1) Mouse-1 is not used to follow links in the grep or compilation buffers.
>
>
Nick Roberts <[EMAIL PROTECTED]> writes:
> I realise that applications like web browsers use mouse-1 to follow
> links, so it is a good idea for Emacs to provide some consistency
> and it works well with Info pages. However, I am not sure if it is
> always appropriate as Emacs users understand tha
I realise that applications like web browsers use mouse-1 to
follow links, so
it is a good idea for Emacs to provide some consistency and it
works well with
Info pages. However, I am not sure if it is always appropriate
as Emacs users
understand that mouse-1 just general
> I realise that applications like web browsers use mouse-1 to follow links, so
> it is a good idea for Emacs to provide some consistency and it works well with
> Info pages. However, I am not sure if it is always appropriate as Emacs users
> understand that mouse-1 just generally moves the cursor,
66 matches
Mail list logo
