Petr Sabata a écrit :
> You could add yet another bloat option for this and use that in dmenu_run.
I don't want to see the names of the first executables (in alphabetical order)
among all the executables found on my path every time I launch a program
through dmenu_run.
So, yes, I'm gonna bloat
Bastien Dejean writes:
> Hi,
>
> I noticed that when dmenu is used as a program launcher (i.e. through
> dmenu_run) the initial display of all the items of stdin is kind of
> annoying.
>
> I'd prefer that the matching items appear only when a non empty search
> string exists.
This would add code
i use a history file with dmenu_run that is displayed before the other
stuff so i can quickly navigate through recently used commands. maybe
that's a compromise for you since it displays useful / often used
items first. and you wouldn't need to patch dmenu itself you can
modify dmenu_run.
annoying, hah!
you suck.
> how about you restrict the number of things coming in on stdin instead
> of puking all over dmenu about this
Because he wants it to still complete to the things in $PATH (or STDIN,
in this case) but doesn't want to see it. I still agree that it's stupid.
In regards to OP: So write a patch that
On Thu, Aug 4, 2011 at 5:56 AM, Bastien Dejean wrote:
> I noticed that when dmenu is used as a program launcher (i.e. through
> dmenu_run) the initial display of all the items of stdin is kind of
> annoying.
how about you restrict the number of things coming in on stdin instead
of puking all over
On Thu, Aug 04, 2011 at 11:56:11AM +0200, Bastien Dejean wrote:
> Hi,
>
> I noticed that when dmenu is used as a program launcher (i.e. through
> dmenu_run) the initial display of all the items of stdin is kind of
> annoying.
>
> I'd prefer that the matching items appear only when a non empty sea
Hi,
I noticed that when dmenu is used as a program launcher (i.e. through
dmenu_run) the initial display of all the items of stdin is kind of
annoying.
I'd prefer that the matching items appear only when a non empty search
string exists.
--
Bastien