From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] various new commands
Date: Sun, 20 Sep 2015 19:41:13 +0100 [thread overview]
Message-ID: <20150920184113.GB2254@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <8737y9pjhz.fsf@mushroom.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
On Sun, Sep 20, 2015 at 01:44:56AM -0700, Chris Brannon wrote:
> Karl Dahlke <eklhad@comcast.net> writes:
>
> > g$
> > go to the last link on the line.
>
> Yep, it seems to follow the principle of least astonishment. I like it.
> I frequently encounter pages with 12 links on a line, so this would be useful!
> i$* belongs, if for no other reason than regularity of
> the command set.
Agreed.
> > > lsl file length
>
> How would these work? Would they just operate on the current file?
> Another alternative would be to have a single lsf command that operates
> kind of like a toggle. Initially, you just see filenames in the buffer,
> like the situation today. But when lsf is invoked, the buffer is rebuilt
> to display stat info alongside each filename.
> Executing lsf again would hide the extra info.
> This one isn't all that important to me either way.
The lsf idea sounds sensible to me.
> > Should I continue to use <func to run an edbrowse function,
>
> You should keep it. Yes, it's ugly, but it means that we never ever ever
> have to worry about colliding with user functions when extending the
> edbrowse command set. Sometimes there's a lot to be said for
> conventions, even ugly ones.
Agreed. Tbh I've never had an issue with that.
What I would like though is some sort of variable support in edbrowse functions.
It'd also be nice if the ok prompt could alter if a command being ran returns
non-zero, and perhaps allow this to be checked in edbrowse functions.
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-09-20 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 5:51 Karl Dahlke
2015-09-20 8:44 ` Chris Brannon
2015-09-20 18:41 ` Adam Thompson [this message]
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=20150920184113.GB2254@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@the-brannons.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).