edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] input text area
Date: Fri, 10 Mar 2017 10:18:05 -0500	[thread overview]
Message-ID: <20170210101805.eklhad@comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

When an input field in a form is a text area it looks like <buffer 4>
I wanted to script something, fill out a form and submit, but the script can't know ahead of time which buffer is selected.
And it can't really scrape buffer 4 off the page and switch to that session.
A new command of some kind is needed.

I thought about this.

i<file

Read the contents of a file into the text buffer.
edbrowse would determine which edbrowse session and put the text there.
We already have this command, but only for text fields, read in the first line of a file into that input field.
So this would not be a new command but a new way to apply it for text areas.
But it's not general, and not as easy to do as the next one.

i@

Switch to the buffer indicated by this text area.
>From there you could read in your file, and do more, maybe edit it in some way. Then switch back to session 1.
But then again, what if you weren't in session 1.
Does the script use i@ again to toggle back to the input form?
So this is less intuitive, less obvious, but more general and more flexible.

On the other hand, I'm not sure I need either of these.
It's been 15 years and this is the first time I've run into this situation,
and even if I had these features, I find I can't execute my scripts for other reasons related to the website.
So it wouldn't help much.
This is just the thought for the day.

Karl Dahlke

                 reply	other threads:[~2017-03-10 15:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170210101805.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --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).