[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vile] how can I learn more about viles 'hypertext' feature?

From: Thomas Dickey
Subject: Re: [vile] how can I learn more about viles 'hypertext' feature?
Date: Tue, 07 Feb 2012 15:51:53 -0500
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Feb 07, 2012 at 09:20:38PM +0100, ben wrote:
> thanks for your quick reply. Unfortunately I can not see how which.rc is  
> helpful. Apparently '&token' is checked for the string 'hypertext' and  
> thats all I can see. But my question is more fundamental.
> - how is hypertext 'produced'? Is it something that can be written in  
> file, or does it exists only in viles buffer?

It's handled in vile by interpreting control sequences
There are a couple of sections in the help-file that discusses the control

  Attribute control sequences (ACS)
  Writing your own filters

in particular this comment:

   The <command> for hypertext commands may be any sequence of characters
   except for newlines and null characters. A null character must terminate
   the hypertext command. The command should be a valid vile command such as
   you might enter into your .vilerc file.

> - how is written? What are the control sequences, that vile recognize   
> as a hypertext command.
> As a summary of these two questions: Is it possible to write hypertext  
> source to be interpreted by vile, similar of what a html file is to a  
> web browser?

It's not an html file (though with some work, one could write a filter
say for lynx that would produce a file that could be read into vile and
act like that).

> Thomas Dickey wrote:
>> On Tue, Feb 07, 2012 at 07:05:32PM +0100, ben wrote:
>>> hi
>>> I don't know if this is too ambitious, but I'd like use viles hypertext
>>> features for different tasks ( a simple wiki, literate programming and a
>>> simple email client ).  AFAIK there are two well known plugins that use
>>> hypertext features: the filebrowser and the grep tool.
>> The which-keywords macro also uses the feature (though much simpler).
>> That's in "which.rc"; looking for places that refer to hypertext in
>> that might be simpler than reading the perl code.
>> I used it to markup the report that shows where a given keywords file
>> is found.  To "click" on the link, I put the cursor on the link and
>> type ^X-z.  Inside the link, there is a "view" command followed by
>> the actual pathname, which is quoted to make this work with filenames
>> that have embedded blanks.

Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]