On 2016-04-18, at 16:13, Rob van der Heij wrote:

>> Easy enough to do (I just did it, several times); just tedious.
>> Has anyone automated this clichi?
>  
> I use "browse" to see the output. I rarely need to massage it with XEDIT
> but would change the pipe to give me what I want to see.
>  
Are we thinking of the same BROWSE?  I didn't know BROWSE could be used
as a pipeline state.  Like:

    PIPE LITERAL TEST | BROWSE  /* ??? */

> It sounds cute to have a device driver to create a new file in the ring, but
> for a generic solution it needs a lot of info (like width, filetype, etc).
> For something specific where you know the data, it certainly works well
> (like assemble the file straight from the editor and write the listing back).
>  
Cute, yes.  And file attributes are a bane.  Even a nuisance for the ">" stage.
How does XEDIT deal with BFS files which have no width, filetype, etc.?
(We don't have BFS configured.)

-- gil

Reply via email to