Allow file URI matching to include extra characters
Brought to you by:
realh
Menu
▾
▴
#63 Allow file URI matching to include extra characters
OK, here's an explanation for this feature request. What would be nice is to be able to match a file URI (as current behaviour does), but allow content after a particular char or regex to be included in the match. Here's some examples to try and clarify:
file:///usr/local/src/some-file.c # this matches with current roxterm
/usr/local/src/some-file.c # no 'file://', matches with current roxterm
/usr/local/src/some-file.c:123 # matches the filename part, nothing after and including ':'
In the last example, the output format is common from tools such as grep, and what I'd like to be able to do is right-click and have my editor open the file at the specified line ('file:line' format is supported by a number of editors including emacs, geany etc). Allowing this feature would enable me to pick and choose files of interest to open from a list of such outputs (something quite common in developer workflows...).
Discussion
Anonymous
Somewhat related, would it be possible to define a regular expression for matching the URI?
I would like to be able to match relative paths (basically match every possible path that contains even a single '/'), even though this would mean a lot of false positives. The links are only visible on mouse over, so I wouldn't mind too much.
This is possible with urxvt (maybe others?), but IMO that terminal looks horrible (even after configuring).
Customisable regexes sounds like a good idea. I'll postpone it for a future release though, because I want to get the 3.0.1 release (supporting vte-2.91) out soon and I haven't got much time for adding other new features.
Sorry I haven't done this yet. I couldn't think of a good way to implement this at first, because each type of URI needs more than one pattern to achieve the current level of flexibility. I have thought of an elegant way to do it now, but it will need quite a bit of work...