> From: "Drew Adams" <[EMAIL PROTECTED]>
> Date: Fri, 14 Jul 2006 12:57:32 -0700
>
> Anyway, I cannot see any difference in behavior of, say, "C-x 5 o"
> (which calls select-frame-set-input-focus, which Drew cited) that
> depends on the value of this variable. Can someone post a recip
> From: "Drew Adams" <[EMAIL PROTECTED]>
> Date: Fri, 14 Jul 2006 12:57:32 -0700
>
> Anyway, I cannot see any difference in behavior of, say, "C-x 5 o"
> (which calls select-frame-set-input-focus, which Drew cited) that
> depends on the value of this variable. Can someone post a recip
(defun select-frame-set-input-focus (frame)
"Select FRAME, raise it, and set input focus, if possible."
(select-frame frame)
(raise-frame frame)
;; Ensure, if possible, that frame gets input focus.
(cond ((eq window-system 'x) (x-focus-frame frame))
((eq window-s
On most applications, scroll bars appear only when there is text to
scroll - that is, they appear only when needed. Emacs should behave
normally in this regard.
In a buffer whose text does not fill the full window vertically, the
vertical scroll bar should disappear. It does not, at least on
Windo
> Anyway, I cannot see any difference in behavior of, say, "C-x 5 o"
> Documenting that would seem to be wrong, as the example I
> sent shows. In that example, if the value is nil, then the mouse
> position does not get set; if non-nil, it gets set.
Is this the example you
Leon, Fri, 07 Jul 2006 15:07:11 -0700:
> With [ GNU Emacs 23.0.0.1 (i686-pc-linux-gnu, GTK+ Version 2.8.19) of
> 2006-07-07 ], I get this warning:
>
> ,
> | Warning (initialization): Building Emacs overflowed pure space. (See
> | the node Pure Storage in the Lisp manual for details.)
> `
>
> There are window managers that does not allow focus changes outside the
> window
> that has the mouse in it, if focus follows mouse. Metacity and sawfish
> calls this mode focus-follows-mouse-strict. In that case, the code
> above moves the mouse to the new window so it gets the focus. It is
> From: "Drew Adams" <[EMAIL PROTECTED]>
> Date: Sat, 15 Jul 2006 07:44:41 -0700
>
> On most applications, scroll bars appear only when there is text to
> scroll - that is, they appear only when needed.
That's slightly inaccurate: the vertical scroll bar does not
disappear, at least not in all GU
> From: "Drew Adams" <[EMAIL PROTECTED]>
> Date: Sat, 15 Jul 2006 09:00:58 -0700
>
> this doesn't
> happen on Windows, at least not for me, and the documentation of the
> Windows API call invoked by w32-focus-frame seems to confirm that.
>
> Dunno about the latter part. Do you mean ju
> Date: Sat, 15 Jul 2006 16:00:03 +0200
> From: martin rudalics <[EMAIL PROTECTED]>
> CC: Eli Zaretskii <[EMAIL PROTECTED]>, emacs-pretest-bug@gnu.org
>
> I think Windows never had a thing like "focus-follows-mouse-strict" or
> "focus-under-mouse". Windows' official non-click philosophy is to
>
>> ... you have to explicitly click on the desktop in order
>>to "give it focus".
>
>
> That's the default, yes. But one can tweak the Registry to force
> Windows behave more like X, in that just entering a window with the
> mouse gives it focus. (I do this on any Windows machine I need to
> wor
> On most applications, scroll bars appear only when there is text to
> scroll - that is, they appear only when needed.
That's slightly inaccurate: the vertical scroll bar does not
disappear, at least not in all GUI applications. What happens is that
the scroll-bar _thumb_ dis
In GNU Emacs 22.0.50.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2006-07-14 on labrador
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
val
On most applications, scroll bars appear only when there is text to
scroll - that is, they appear only when needed. Emacs should behave
normally in this regard.
This would be very hard to implement; and the changes in window width
could be quite annoying to Lisp programs.
In a buf
Thanks for starting to explore this issue.
Because it only finds `defun' calls, it fails to find other constructs
that define functions or macros. Also, it would get rather confused
when dealing with top-level forms that don't define functions at all:
it just skips them.
The example suggests tha
15 matches
Mail list logo
