edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: edbrowse-dev@edbrowse.org
Subject: Re: [edbrowse-dev] spurious empty buffers from textareas
Date: Thu, 10 Jan 2019 01:15:54 +0100	[thread overview]
Message-ID: <20190110001554.GA5472@nautica> (raw)
In-Reply-To: <31c77dba-b68b-d90d-288a-2467b86dee78@pcdesk.net>

Tyler Spivey wrote on Wed, Jan 09, 2019:
> What will this do if there's text in that field already? My vote
> would be to say something like <buffer text>, and then let the
> command just put that in. 99% of the time I'm not going to care
> about whatever pre-filled text there is unless I'm filling out the
> form.

Agreed to that, the command whatever it is probably should insert the
text in the buffer at the time we use it.

I'd actually be daring and suggest that the command would also print
what the current buffer is and switch to the new buffer.
There are two things here:
 - printing the current buffer is mostly a personal opinion. I don't use
buffers all that much so when I do I'm always a bit unsure where I
should come back to; it's not really necessary. I might actually just
have been missing that 'e' without a number prints it..
 - switching automatically is more interesting, but also probably more
controversial. I think if someone says itext or whatever they will want
to use that buffer, so they will eventually switch to it, so why not
now? But on the other hand a command switching buffers might surprise
new people...


      reply	other threads:[~2019-01-10  0:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 12:18 Karl Dahlke
2019-01-09 12:42 ` Chuck Hallenbeck
2019-01-09 17:53 ` Tyler Spivey
2019-01-10  0:15   ` Dominique Martinet [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:

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

  git send-email \
    --in-reply-to=20190110001554.GA5472@nautica \
    --to=asmadeus@codewreck.org \
    --cc=edbrowse-dev@edbrowse.org \


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