[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ranger-users] Trash

From: Miodrag Milic
Subject: Re: [Ranger-users] Trash
Date: Mon, 4 Mar 2013 14:38:42 +0100

Yeah, I did try -s parameter and wondered why does it still flicker 

Thanks for the update. I definitely prefer the rc.conf way.

On Mon, Mar 4, 2013 at 2:34 PM, Roman Z. <address@hidden> wrote:
On Mon, Mar 04, 2013 at 02:08:01PM +0100, Miodrag Milic wrote:
> That is showing the console for short which is extremely annoying.
> especially if you do it multiple times in a row.
> I tried with shell -f which doesn't show it, but then it doesn't update the
> screen. The next was
>   chain shell -f trash %s; reload_cwd
> but that didn't work either so I did
>  chain shell -f trash %s; eval time.sleep(0.2); reload_cwd
> but I had to previously import time in commands.py (I am just learning
> python, perhaps there is other way).
> however, that blanked the screen during sleeping.
> So I just resorted to command.py.
> So... could you provide simple mapping which doesn't flicker ?

Good point.  In fact, there is no good way to do that at the moment. The
rationale for showing the console is that there's no way of knowing
beforehand whether the program prints something or not, or if the
command is interactive or not.

But there is a flag for :shell to silence the output: "-s".  It seems
predestined for this task.  If there is no output, there is no need to
switch to the console.  I just pushed a change that implements it, you
can now use "shell -s trash-put %s" without flickering.

Now that I think about it, renaming the flag to "-q" might be
appropriate since it's used in many other programs to inhibit the

reply via email to

[Prev in Thread] Current Thread [Next in Thread]