Hello!
> Message de Kris Maglione: mar. 17/08/10, 19:19:10 -0400
> This behavior is achievable, but considerably magnitude more
> complex.
Aha.
> However, in the case of the example you provided, I don't think it's
> that important, given that there are few enough options that you can
> tab be
On Tue, Aug 17, 2010 at 03:56:38PM +0200, LuX wrote:
OK, let us call:
- 'post' the last script I have posted, on:
http://lists.suckless.org/dev/1008/5609.html
- 'patch' and 'script' the patch and script you posted on:
http://lists.suckless.org/dev/1008/5610.html
I copied 'post' and 'patch' fro
Hello!
Tue, 17 Aug 2010 06:26:37 -0400, Kris Maglione wrote:
> The patch was against your script.
OK, let us call:
- 'post' the last script I have posted, on:
http://lists.suckless.org/dev/1008/5609.html
- 'patch' and 'script' the patch and script you posted on:
http://lists.suckless.org/dev
On Tue, Aug 17, 2010 at 12:04:28PM +0200, LuX wrote:
I'd suggest some slight changes, though:
*** Here is a patch (diff file)
The following will do what you want:
*** Here is a full script
I'm sorry but I'm a little bit confused here (recall that I'm somewhat
a beginner in this area). It seem
Hello!
on, 16 Aug 2010 21:22:18 -0400, Kris Maglione wrote:
> But our file is a FIFO, anyway. Its contents never touch the disk. It
> would probably be better in ~/.wmii/menu_fifo or the like, though.
I see.
I put files wi_cli.sh, fifo and opts, with obvious meanings, in
'$HOME/.wmii/wi_cli/'.
On Tue, Aug 17, 2010 at 02:15:13AM +0200, LuX wrote:
On Sun, 15 Aug 2010 18:51:55 -0400, Kris Maglione wrote:
Yes, I already fixed that problem when I made it into an example
file for distribution. Attached.
I have a few unessential remarks, if you allow me:
Of course.
- Although I don't
Hello!
@Arian Kuschki: Thank you too, for the .inputrc trick.
On Sun, 15 Aug 2010 18:51:55 -0400, Kris Maglione wrote:
> Yes, I already fixed that problem when I made it into an example
> file for distribution. Attached.
I have a few unessential remarks, if you allow me:
- Although I don't un
Hi!
On Sun, 15 Aug 2010 18:51:55 -0400, Kris Maglione wrote:
> Bash completion is actually written in bash, so it's very
> customizable.
[..]
> Just add this to ~/.inputrc:
You are changing my life!
I found it now in 'man bash'. I never imagined before that this could
exist.
> I take it you
Excerpts from LuX's message of 2010-08-16 00:37:54 +0200:
> Example: In bash I have always been missing a history behaving like in
> vim. Let me explain this. If you have typed a long command 'cmd' at
put
"\C-n": history-search-forward
"\C-p": history-search-backward
and/or
"\e[B":history-sea
On Mon, Aug 16, 2010 at 12:37:54AM +0200, LuX wrote:
On Thu, 12 Aug 2010 21:19:52 -0400, Kris Maglione wrote:
But if you're looking for a start, this is the above modified to
(crudely) complete a command and then files in the current
directory:
I have an issue with this second variant, which
Hello!
On Thu, 12 Aug 2010 21:19:52 -0400, Kris Maglione wrote:
> But if you're looking for a start, this is the above modified to
> (crudely) complete a command and then files in the current
> directory:
I have an issue with this second variant, which I didn't notice first
and am unable to sol
On Sun, Aug 15, 2010 at 06:25:49AM +, carmen wrote:
I couldn't have said it better myself.
--
Kris Maglione
Lisp has jokingly been called "the most intelligent way to misuse a
computer". I think that description is a great compliment because it
transmits the full flavor of liberation: i
On Thu, Aug 12, 2010 at 09:19:52PM -0400, Kris Maglione wrote:
I might add a horizontal mode to wimenu. I'm personally not very fond of
it, but others seem to find it useful and it's a simple enough change.
I've done this, with zero new net lines of code no less, but it
needs to be cleaned up
On Sat, Aug 14, 2010 at 12:34:41AM +0200, LuX wrote:
On Thu, 12 Aug 2010 21:19:52 -0400, Kris Maglione wrote:
if you're looking for a start, this is the above modified to (crudely)
complete a command and then files in the current directory
This second variant is fantastic! It allows me to sele
Hello!
On Thu, 12 Aug 2010 21:19:52 -0400, Kris Maglione wrote:
> if you're looking for a start, this is the above modified to (crudely)
> complete a command and then files in the current directory
This second variant is fantastic! It allows me to select a command
with wimenu, add some options, f
Hello!
On Fri, 13 Aug 2010 17:39:12 +0100, Connor Lane Smith wrote:
> An important thing to remember is that a feature does not need to be
> in mainline for you to patch it in.
I'm not at all a programmer, I have no ability for patching a program
like this, but I accept this point.
I accept al
On Thu, Aug 12, 2010 at 09:19:52PM -0400, Kris Maglione wrote:
Yes... Unfortunately awk dies on SIGPIPE in that example, so it never
runs the END block. This slight variation should work:
wimenu -c fifo; fflush(fifo)
}
//
# Push out a new set of completions
On Thu, Aug 12, 2010 at 10:51:59PM +0200, LuX wrote:
I would really like to use the 'custom completion' feature documented
in the man page of wimenu-3.9.2, just as in the provided example:
Unfortunately the example script given there goes far beyond my
skills. I have copied and pasted it in a fi
Hello list!
I would really like to use the 'custom completion' feature documented
in the man page of wimenu-3.9.2, just as in the provided example:
> Let's assume that a script would like to provide a menu with
> completions first for a command name, then for arguments to that
> command.
Unfo
20 matches
Mail list logo
