edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] various new commands
Date: Sun, 20 Sep 2015 01:44:56 -0700	[thread overview]
Message-ID: <8737y9pjhz.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150820015101.eklhad@comcast.net> (Karl Dahlke's message of "Sun, 20 Sep 2015 01:51:01 -0400")

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.

> > 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.

> 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.

-- Chris

  reply	other threads:[~2015-09-20  8:41 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 [this message]
2015-09-20 18:41   ` Adam Thompson

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=8737y9pjhz.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.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).