Re: Per request - Brian & West (no receipt either)

Mattias Westlund wrote:
> Anyway, back on topic:
> 
> Paul, that lsxcommand "mod" is really freakin cool. A couple of 
> questions though:
> 
> 1. The *watchfile setting isn't working here; the history label does not 
> get updated. Also tried updating it with CommandOnCommand, but no go. Am 
> I missing something?

I see you got it firgured out, so I will skip answering this. I believe 
the module started out as a recycle only bang. Now of course it can do 
any bang.

> 2. Have you (or anyone else) experimented with stripping out those 
> numbers at the beginning of each line? First I thought it could be 
> possible somehow using a modifier but I couldn't get my head around the 
> syntax when using [lastline].
> 
> 3. A really neat thing would be making those history entries 
> clickable... i.e. so you can click them hyperlink-style and have the 
> commands entered into lsxcommand. But my head spins when trying to think 
> of a way to make that happen. Anyone have any ideas?

Both of these were done by xcal back when I first made this little mod. 
I never got his method to work, but since you are a *bit* more advanced 
of a user, you may have more luck. Below is the posting from Steve:

Steve wrote:
 > For kicks, I made something to parse the history file.  It will create
 > the syntax you need to display it in a label as a clickable link.  I'm
 > sure this could be done with lslua... but, anyway, this was fun to 
make. ;)
 >
 > You can get the file here:  http://msu.edu/~tower/steve/lsxcparser.exe
 >
 > Syntax is:  lsxparser.exe "input_file" "output_file" [optional "1" for
 > link tooltips]
 > And, info can be brought up with:  lsxcparser.exe /?
 >
 > Example of use:
 >
 > *Label history
 > historyX 20
 > historyY 40
 > historyAutoWidthMode left
 > historyAutoHeightMode top
 > historySolidColors FFFFFF A6A6A6 000000
 > historySolidBevelSize 3
 > historyBorders 6
 > historyText "[line('$ThemeDir$output.txt', '1', '10')]"
 > historyAlwaysOnTop
 > historyOnLeftClick !history_update
 >
 > *Script bang !history_update
 >    *Script exec "$ThemeDir$lsxcparser.exe" "$CommandHistoryFile$"
 > "$ThemeDir$output.txt" "1"
 >    *Script exec !pause 1500
 >    *Script exec !labelrefresh history
 > *Script ~bang
 >
 > Note:  Ideally, you'd use CommandOnCommand !history_update.
 > Unfortunately, CommandOnCommand is executed before the history is
 > written.  =\
 >
 >
 > Paul wrote:
 >> Steve wrote:
 >>> Hey, that's really cool.  Did you make the text clickable?  Like
 >>> click the text and it runs the command?
 >>>>
 >>
 >> Hey now, you are asking alot of me there. The lines above (the
 >> history) is only really the following line:
 >>
 >> [lastLine('$CommandHistoryFile$', '10')]
 >>
 >> i wouldn't know how to make them action links. Besides, I can just hit
 >> arrow up 1 - 10 times to get the !bang so it is not too bad. I can
 >> look into it later though.
 >
 >

> /West
> 
> Brian Wolven wrote:
>> Mattias Westlund wrote:
>>> I wanna be DigBaddy, gangsta rapper and LS themer extraordinaire.
>>
>> A Swedish gangsta rapper - now *there's* something you don't see every 
>> day.
>>
>> Can I be OTS2pac?
>>
>>
>> ---------------------------------------------------------------------
>>    Can't Unsubscribe? Check http://desktopian.org/listunsub.html
>>        LS List Homepage: http://wuzzle.org/list/litestep.php
>>            Get the LS FAQ: http://lsfaq.shellfront.org
>>
>>
> 
> ---------------------------------------------------------------------
>    Can't Unsubscribe? Check http://desktopian.org/listunsub.html
>        LS List Homepage: http://wuzzle.org/list/litestep.php
>            Get the LS FAQ: http://lsfaq.shellfront.org
> 
> 


---------------------------------------------------------------------
    Can't Unsubscribe? Check http://desktopian.org/listunsub.html
        LS List Homepage: http://wuzzle.org/list/litestep.php
            Get the LS FAQ: http://lsfaq.shellfront.org