Re: Paul's & xcal's lsxcommand mojo

Mattias Westlund wrote:
> OK, I've been playing with Paul's/xcal's lsxcommand-enhancing stuff. 
> It's a great way of making lsx both more useful and cooler-looking, but 
> there is still a few things that I can't seem to figure out.

That's me man, Big-Dad-E ... Supra-genius ...substantial pimp Daddy... 
Trendsetter.

> First of all: updating the history label. I've been racking my brain 
> trying to think of a way of doing that when commands are launched from 
> lsxcommand. As xcal noted, it seems that CommandOnCommand is run 
> *before* anything is written to the history file. As for autorecycle, I 
> just can't get that module to work. I've tried setting it to watch 
> lsxcparser's output file, but nothing happens. Not a damn thing. A 
> possible way of doing it -- and I'm just theorizing here -- might be 
> using a timer. IOW, having CommandOnCommand start a timer that after, 
> say, 2000ms updates the history label. But maybe that won't make any 
> difference. Does anyone have any bright ideas?

I just have it set to watch the lsxCommand history file.

*watchfile $CommandHistoryFile$ !LabelUpdate CommandBack_

CommandBack_ being the label with the history as text. That's it. No 
other !bangs or complicated configuration. Of course the downside is 
that you cannot have the clickable history. Me personally, I am a hotkey 
user so arrow up/down is my preference.

Maybe it is a cursed timing issue? Try maybe
*watchfile $CommandHistoryFile$ !execute [!pause 300][!LabelUpdate 
CommandBack_]

The problem I remember having with xcal's config and executable was that 
my Litestep would just hang until I killed litestep.exe.


> Secondly -- and this is more of a general xLabel obeservation -- it 
> seems that hrefhoverconfig isn't working. I wanted to highlight the 
> history entries when hovering over them, but no matter what tags or 
> chars I try, the label just ignores my efforts. I havent used that 
> setting since xLabel 3.6.2, so I'm wondering: could it be broken or is 
> there some other setting that needs to be activated for it to work?

Don't know as I never used it.

> And finally -- xcal, if you're reading this: It seems that lsxcparser 
> only plucks ten lines from the history file. Is there some way to 
> increase this number? I normally have a longer lsx history than that, 
> and having the parser fetch *all* lines (except [lsxcommand] of course) 
> would really make more sense. Any chance of seeing an update to the 
> parser? ;)
> 
> 
> /West

Good luck with it!

> 
> ---------------------------------------------------------------------
>    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