From: "Fco. J. Ballesteros" <nemo@gsyc.escet.urjc.es>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: but tom-2 repeat cmd feature?
Date: Thu, 27 Jul 2000 05:14:52 -0500 [thread overview]
Message-ID: <14719.64908.755161.847689@nautilus.dat.escet.urjc.es> (raw)
Wouldn't it be nice if the button-2 menu could have an entry to repeat
the last command in the ~~sam~~ window?
I found myself repeating <move mouse> <click> "|fmt" just to reformat
paragraphs in a LaTeX document I was editing.
Anyone made that change to sam? Or is there a better way to do it?
(Doing a single |fmt when done with the modifications is not an option
because there are sections of the document that shoudn't be fmt'd).
regards
--
() ascii ribbon campaign - against html mail
/\ - against microsoft attachments
next reply other threads:[~2000-07-27 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-27 10:14 Fco. J. Ballesteros [this message]
2000-07-28 1:27 ` Paul Jackson
2000-07-28 6:52 ` Steve Kilbane
2000-07-29 21:41 ` James A. Robinson
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=14719.64908.755161.847689@nautilus.dat.escet.urjc.es \
--to=nemo@gsyc.escet.urjc.es \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).