edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@edbrowse.org
Subject: Re: [edbrowse-dev] spurious empty buffers from textareas
Date: Wed, 9 Jan 2019 07:42:56 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.> (raw)
In-Reply-To: <20190009071846.eklhad@comcast.net>

I vote yes. It's a small price to pay for long-term stability, IMO.
My preference for the new command would be ib, but I would be okay with

Many thanks.


On Wed, 9 Jan 2019, Karl Dahlke wrote:

> These have annoyed me for quite a while, and come to find they annoy others as well.
> As per our chat discussions, I made a change, but it's a UI change so should be described here.
> (Not everyone is on chat.)
> A fill out form with a textarea use to allocate a buffer for that area at browse time, looking like <buffer 7>
> It now waits to see if you're actually going to use it, since 90% of the time you don't.
> It begins life as <buffer ?>
> An itext (for input text) command  allocates a buffer and changes it to <buffer 7>
> Then you can write text in buffer 7 and submit the form like before.
> It's one more step for something that is rarely done,
> but it prevents a ton of empty buffers from accumulating.
> I have no strong feelings about the actual command name.
> itext (input text)
> ibuf (input buffer)
> iw (input write)
> ita (input textarea)
> Long as it starts with i I'm ok.
> If you change line 760 in decorate.c the old behavior returns.
> I'm not documenting any of this until a majority thinks it's a good idea.
> My vote is yes but others may disagree.
> Karl Dahlke

   Here In Northeast Ohio, The Moon is Waxing Crescent (10% of Full)
    Sent from Nick's missing iPhone.

  reply	other threads:[~2019-01-09 12:43 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 [this message]
2019-01-09 17:53 ` Tyler Spivey
2019-01-10  0:15   ` Dominique Martinet

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=alpine.LNX. \
    --to=chuckhallenbeck@gmail.com \
    --cc=edbrowse-dev@edbrowse.org \
    --cc=eklhad@comcast.net \


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