all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <bug-gnu-emacs@gnu.org>
Subject: bug#4906: 23.1; strokes.el problems
Date: Wed, 11 Nov 2009 10:08:54 -0800	[thread overview]
Message-ID: <C6E8ADA7103D4A1C9FE5ACA777CC2D51@us.oracle.com> (raw)

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)'
 







             reply	other threads:[~2009-11-11 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87pr7ju6a3.fsf@stupidchicken.com>
2009-11-11 18:08 ` Drew Adams [this message]
2009-11-15 16:05   ` bug#4906: marked as done (23.1; strokes.el problems) Emacs bug Tracking System

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C6E8ADA7103D4A1C9FE5ACA777CC2D51@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=4906@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.