Re: [Vimprobable-users] two ideas to improve the quickmarks

[Marcos C. <vim...@pr...>]

En/Je/On 2013-04-29 17:20, Daniel Carl escribió / skribis / wrote :

> But we must keep the in mind to have the ability to use all parametes
> for the shortcuts together, to not break the search-engine feature.  I
> suggest to use %0 as placeholder for all parameters, and %1-%9 as
> placeholder for single parameters. 

You're right. But if several parameters were finally implemented, and
the space were used as parameter separator, then one single placeholder
(the one for the first parameter, %s, %0 or %1 or whatever) in the
config command would be enough, meaning just "everything till the end of
line".  Of course a specific placeholder for every parameter would be
more versatile. Using %0 for the whole string lets the system to be
expanded in the future to accept individual params with %1-%9.

> My second concern goes to the placeholder format. Does Elinks use the '%'-Char
> to mark placeholders?

Yes it does:

	%c in the string means the current URL
	%s in the string means the whole argument to smartprefix
	%0,%1,...,%9 means argument 0, 1, ..., 9
	%% in the string means '%'

> I think it isn't easy to distinguisch %x from url entities like (%20
> for a space). Maybe we should change the placeholder to something else
> $0 or so.

Good point.  I suppose any hex encoded char (format %[0-9A-F][0-9A-F])
is skipped by Elinks, but I didn't try. I think ambiguous cases must be
unusual... a parameter before a hex digit... Something like this, where
"%1" represents the decade's digit, "%2" the month and "%3" the day:

	http://domain.com/archive/20%10/%2/%3

"%1" before the "0" char is confusing, but AFAIK "%10" (16 decimal) is
not a valid char in a URL.
	
This is worst, "%2"+0 can be interpreted as "%20" (32 decimal, space):

	http://domain.com/archive/user_%1/20%20/%3/%4

Some investigation is required.

Marcos

-- 
http://programandala.net