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]   wordexp again
Date: Fri, 17 Apr 2015 18:25:31 -0400	[thread overview]
Message-ID: <20150317182531.eklhad@comcast.net> (raw)
In-Reply-To: <20150417215826.GF5949@toaster.adamthompson.me.uk>

Reversing the sense of the leading ` is, I think, an interesting idea.
There are no side effects unless you ask for them, and it would fix a bug
that you introduced, wherein r5,
to read the fifth buffer into the current buffer, no longer works.
It doesn't work because 5 runs through wordexp and there is no file called 5.
I use this feature a hundred times a day, to cut and paste text
between sessions.
Anyways it fails now because 5 runs through wordexp,
but it use to work,
and would work again if such lines did not go through wordexp by default,
either because my syntax checker was back in place,
or because you had to indicate so with a leading `.
An unknown for me is how often I automatically, and without thinking,
use * to edit or read a file; I just pattern match automatically,
and I can see myself cursing and having to type it in again with a leading `
and by that time I probably could have just typed in the filename. Damn!
and I'd be annoyed because here again it is different from the shell.
I guess I'll have to sleep on this for a night or two,
or maybe play with it in its different modes for a week or two,
to get a sense of things.
One thing I have to do right away is fix the r5 bug,
in one way or another.
Reading and writing among buffers just has to work for me.

Karl Dahlke

  reply	other threads:[~2015-04-17 22:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 21:40 Karl Dahlke
2015-04-17  7:12 ` Adam Thompson
2015-04-17 12:50   ` Adam Thompson
2015-04-17 13:33     ` Karl Dahlke
2015-04-17 17:59       ` Adam Thompson
2015-04-17 13:47     ` Karl Dahlke
2015-04-17 18:01     ` Karl Dahlke
2015-04-17 21:34       ` Adam Thompson
2015-04-17 21:58         ` Adam Thompson
2015-04-17 22:25           ` Karl Dahlke [this message]
2015-04-17 22:43             ` Adam Thompson
2015-04-17 23:14               ` Karl Dahlke
2015-04-17 22:28           ` Adam Thompson
2015-04-17 22:39             ` Karl Dahlke
2015-04-18 10:53               ` Adam Thompson
2015-04-18  4:18     ` Karl Dahlke
2015-04-18 10:49       ` Adam Thompson
2015-04-18 11:34         ` Karl Dahlke
2015-04-18 13:09           ` Adam Thompson
2015-04-18 19:33             ` Chris Brannon
2015-04-18 20:05               ` Adam Thompson
2015-04-18 23:03                 ` Chris Brannon
2015-04-18 12:36         ` Karl Dahlke
2015-04-18 12:54           ` Adam Thompson
2015-04-18 13:09             ` Karl Dahlke
2015-04-18 13:24               ` Adam Thompson
2015-04-18 13:45                 ` Karl Dahlke
2015-04-18 17:44                   ` Adam Thompson
2015-04-18 19:48                     ` Karl Dahlke
  -- strict thread matches above, loose matches on Subject: below --
2015-01-09 22:44 Karl Dahlke
2015-01-09 22:19 Karl Dahlke
2015-01-09 22:29 ` Chris Brannon
2015-01-09 21:16 Chris Brannon

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=20150317182531.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).