bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#4906: marked as done (23.1; strokes.el problems)


From: Emacs bug Tracking System
Subject: bug#4906: marked as done (23.1; strokes.el problems)
Date: Sun, 15 Nov 2009 16:05:05 +0000

Your message dated Sun, 15 Nov 2009 11:00:52 -0500
with message-id <87pr7ju6a3.fsf@stupidchicken.com>
and subject line Re: 23.1; strokes.el problems
has caused the Emacs bug report #4906,
regarding 23.1; strokes.el problems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
4906: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=4906
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
--- Begin Message --- Subject: 23.1; strokes.el problems Date: Wed, 11 Nov 2009 10:08:54 -0800
emacs -Q
 
Visit a directory with Dired.
 
M-x load-library RET strokes RET
 
M-x strokes-global-set-stroke RET
 
That raises the error "Buffer is read-only". Bug #1.
 
C-x b RET, to move to *scratch*.
 
M-x strokes-global-set-stroke RET
 
That raises the error "Wrong type argument: window-configuration-p, nil. Bug #2.
 
Start over: emacs -Q, then, in buffer *scratch*:
 
M-x strokes-global-set-stroke RET
 
Trace a line with mouse-1 pressed, then click mouse-3. Enter a command
name, such as `copy-region-as-kill'.
 
The text that was in the *scratch* buffer is now gone, and replaced by
the single character `@'. (And there is no undo in this buffer.) Bug #3.
 
But at least the stroke got defined. So now we can use it, via
`S-mouse-2).
 
But the doc and commentary say that when you use a stroke (by dragging
S-mouse-2), you will see the stroke traced, provided that
`strokes-use-strokes-buffer' is non-nil. This is not true. At least on
Windows, I see nothing traced at all the *Strokes* buffer remains
visibly empty (whitespace) throughout. Bug #4.
 

In GNU Emacs 23.1.1 (i386-mingw-nt5.1.2600)
 of 2009-07-29 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.4)'
 




--- End Message ---
--- Begin Message --- Subject: Re: 23.1; strokes.el problems Date: Sun, 15 Nov 2009 11:00:52 -0500
> emacs -Q
> Visit a directory with Dired.
> M-x load-library RET strokes RET
> M-x strokes-global-set-stroke RET
> That raises the error "Buffer is read-only". Bug #1.
> C-x b RET, to move to *scratch*.
> M-x strokes-global-set-stroke RET
> That raises the error "Wrong type argument: window-configuration-p, nil. Bug 
> #2.
> Start over: emacs -Q, then, in buffer *scratch*:
> M-x strokes-global-set-stroke RET
> Trace a line with mouse-1 pressed, then click mouse-3. Enter a command
> name, such as `copy-region-as-kill'.
> The text that was in the *scratch* buffer is now gone, and replaced by
> the single character `@'. (And there is no undo in this buffer.) Bug #3.
> But at least the stroke got defined. So now we can use it, via
> `S-mouse-2).
> But the doc and commentary say that when you use a stroke (by dragging
> S-mouse-2), you will see the stroke traced, provided that
> `strokes-use-strokes-buffer' is non-nil. This is not true.

All these bugs were due to a single oversight in
strokes-update-window-configuration.  I've just checked in a fix.
Thanks for the bug report.

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]