From: Silas McCroskey <inkswinc@gmail.com>
To: 9fans <9fans@9fans.net>, eekee57@fastmail.fm, ftrvxmtrx@gmail.com
Subject: Re: [9fans] Sam tricks (was: Alternative to fine-grained mouse usage?)
Date: Thu, 1 Jul 2021 14:59:57 -0700 [thread overview]
Message-ID: <CAHjwAuz3h6AW37=wG1w43m_8s_biT9aOh-spw35jUCROBqzk8g@mail.gmail.com> (raw)
In-Reply-To: <CD50380DE8F8C23967970C4AA373BC5D@gmail.com>
> often switching files, Sam's menus are practically worse than Acme
> The weakest point in sam -d is still switching files, you have to type
> whole filenames
X/pathregex/b
sam will dump a warning about an expected blank, but it'll otherwise
do what you hope for (switch to the open file matching the regex).
> Loading a rc file with a bunch of "fn ... {" simplifies things quite a lot in general
Seconded on ^ and _ (though I rarely use the latter). I use "bind -b
lib/sam /bin" within sam, though, as I prefer separate files so I can
organize stuff by language and such (e.g. ^c/ind indents . with tabs,
^py/ind indents . with spaces, and language-specific poor-man's
parsing for stuff like selecting the entire body of the function
you're in). Also nice: a lot of my "scripts" just use "#!/bin/sed 1d"
or "#!/bin/sed /^#/d" so they don't need to mess with shell evaluation
at all, e.g.:
mystia% cat lib/sam/d
#!/bin/sed /^#/d
,> diff -c $% /fd/0
(outputs the diff between the buffer and the file -- mostly ends up in
/tmp/sam.err)
mystia% cat lib/sam/gd
#!/bin/sed /^#/d
!@{cd `{basename -d $%} && git/diff `{basename $%}}
(outputs the git diff of the current file -- mostly ends up in /tmp/sam.err)
- sam-d
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T274bbf3037e0edb1-Mb6b866d13c89e6a36656b2e3
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-07-01 22:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 1:15 [9fans] Alternative to fine-grained mouse usage? Dworkin Muller
2021-07-01 2:51 ` umbraticus
2021-07-01 4:36 ` Paul Lalonde
2021-07-01 5:05 ` umbraticus
2021-07-01 10:36 ` hiro
2021-07-03 9:09 ` Dworkin Muller
2021-07-03 9:31 ` hiro
2021-07-01 11:12 ` igor
2021-07-01 17:48 ` Ethan Gardener
2021-07-01 18:01 ` Sigrid Solveig Haflínudóttir
2021-07-01 21:59 ` Silas McCroskey [this message]
2021-07-02 15:03 ` silas poulson
2021-07-02 18:06 ` Ethan Gardener
2021-07-02 18:54 ` Silas McCroskey
2021-07-03 2:29 ` umbraticus
2021-07-03 11:52 ` Ethan Gardener
2021-07-03 11:48 ` Ethan Gardener
2021-07-03 16:32 ` silas poulson
2021-07-03 21:33 ` Ethan Gardener
2021-07-03 23:19 ` Dworkin Muller
2021-07-04 9:42 ` Ethan Gardener
2021-07-02 2:20 ` Cyber Fonic
2021-07-07 3:14 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-07-12 4:01 ` Dworkin Muller
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='CAHjwAuz3h6AW37=wG1w43m_8s_biT9aOh-spw35jUCROBqzk8g@mail.gmail.com' \
--to=inkswinc@gmail.com \
--cc=9fans@9fans.net \
--cc=eekee57@fastmail.fm \
--cc=ftrvxmtrx@gmail.com \
/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).