[ jEdit-devel ] [ jedit-Feature Requests-1541997 ] Document differences between globs and REs

[SourceForge.net <no...@so...>]

Feature Requests item #1541997, was opened at 2006-08-17 16:00
Message generated for change (Comment added) made by vampire0
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350588&aid=1541997&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Björn Kautler (vampire0)
Assigned to: Alan Ezust (ezust)
Summary: Document differences between globs and REs

Initial Comment:
Document differences between file name globs and 
regular expressions while making clear that globs are 
translated to REs and used as REs internally.

Sorry if this is a dupe, but I have many bugs to post 
and am too lazy to check them all for dupes 
currently. :-)

OS: Windows XP
Java Version: Sun Java 1.5.0_06-b05
jEdit Version: SVN Revision 6684 (4.3pre7)


----------------------------------------------------------------------

>Comment By: Björn Kautler (vampire0)
Date: 2007-03-09 00:10

Message:
Logged In: YES 
user_id=918212
Originator: YES

Because it is very much easier to understand globs for people that are
used to Regexes if it is documented how the glob is transformed to a regex.

----------------------------------------------------------------------

Comment By: Robert Schwenn (rschwenn)
Date: 2007-03-07 21:47

Message:
Logged In: YES 
user_id=1486645
Originator: NO

I find the doc useful.

Describing filefilters using Globs is simpler than using RegExp. So, why
making documentation more complicated than it have to be?


----------------------------------------------------------------------

Comment By: Björn Kautler (vampire0)
Date: 2007-03-07 01:09

Message:
Logged In: YES 
user_id=918212
Originator: YES

I don't think so. ;-)
I meant to describe exactly what is converted to what, meaning the exact
steps how a glob is translated to a regex. This way people that know
regexes but not globs can very easy understand how to write globs right and
what regex features they can use.

Btw. I think as part of this feature request we should add a
(?<someCharacterHere>) compilerflag or something similar like regexes have
them e. g. for multilineness or caseinsensitivity. And if this flag is set,
the glob should not be translated, but treated as a regex, just without
that flag. This way we satisfy the people that want to use regexes instead
of globs very easily. :-)

While I think about it, don't let us make it like the regex compiler
flags, because if we use a different syntax like {thisIsARegex} or
something veeeeeeeeery much shorter *g* it is easier and faster to remove
and treat the remaining part as regex. If it is exactly the same syntax as
the regex flags, it could be mixed up and used wrong.

----------------------------------------------------------------------

Comment By: SourceForge Robot (sf-robot)
Date: 2007-02-15 04:20

Message:
Logged In: YES 
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2007-02-01 01:20

Message:
Logged In: YES 
user_id=935841
Originator: NO

I did update Appendix D: Glob Patterns (using jEdit) users guide.
Is it satisfactory now?

jEdit uses glob patterns similar to those in the various Unix shells to
implement file name filters in the file system browser. Glob patterns
resemble regular expressions somewhat, but have a much simpler syntax. The
following character sequences have special meaning within a glob pattern:
? matches any one character
* matches any number of characters
{!glob} Matches anything that does not match glob
{a,b,c} matches any one of a, b or c
[abc] matches any character in the set a, b or c
[^abc] matches any character not in the set a, b or c
[a-z] matches any character in the range a to z, inclusive. A leading or
trailing dash will be interpreted literally
In addition to the above, a number of java.util.regex “character class
metacharacters” may be used, but their usefulness is limited since the
regex quantifier metacharacters (asterisk, questionmark, and curly
brackets) are redefined to mean something else in glob language.
\w matches any alphanumeric character
\s matches a space or horizontal tab
\d matches a decimal digit
\S matches a non-space, non-control character
Here are some examples of glob patterns:
* - all files.
*.java - all files whose names end with “.java”.
*.[ch] - all files whose names end with either “.c” or “.h”.
[^#]* - all files whose names do not start with “#”.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350588&aid=1541997&group_id=588