edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] wordexp again
Date: Sat, 18 Apr 2015 13:54:13 +0100	[thread overview]
Message-ID: <20150418125413.GL5949@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20150318083645.eklhad@comcast.net>

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

On Sat, Apr 18, 2015 at 08:36:45AM -0400, Karl Dahlke wrote:
> > I notice you miss out the ~whatever expansion here,
> 
> No, I get that for free.
> It's handled by glob().
> And it works, and it's pretty cool.
> I don't have a lot of use for it but I like it.

Ok, never knew glob did that, that's cool.

One thing puzzles me about the changes though:
 
/* But first see if the user wants to glob */
	if (varline[0] == '~') {
		char c = varline[1];
		if (!c)
			goto doglob;
		if (c == '/')
			goto doglob;
		if (isalphaByte(c))
			goto doglob;
	}
	for (s = varline; *s; ++s)
		if (strchr("*?[", *s) && (s == varline || s[-1] != '\\'))
			goto doglob;

noglob:
	*expanded = varline;
	return true;

I thought we were using globbing so that we didn't have nasty side-effects,
and I'm not entirely sure what this check solves.
If there are metacharacters in the expanded line by this point and they're
unescaped then we'll glob, otherwise they're correctly escaped and thus
globbing wouldn't do any harm anyway.
In addition glob appears to handle a ] without a [ etc,
so again this check seems somewhat redundant.
As for the r5 (or r<buffer_number>) problem which is what I guess this is
trying to solve, that number shouldn't have gone anywhere near this function
since, as far as I know, r<filename> is illegal and should be r <filename> anyway.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-04-18 12:55 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
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 [this message]
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=20150418125413.GL5949@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).