[Top][All Lists]

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

Re: [Ranger-users] ranger: how-tos or cheat-sheet

From: ping
Subject: Re: [Ranger-users] ranger: how-tos or cheat-sheet
Date: Wed, 06 Mar 2013 11:58:17 -0500
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3

On 3/5/2013 6:15 PM, Roman Z. wrote:
But to answer your question, it depends whether you use the command
often or rarely.  If you just want to type it in a few times, simply
write "@tcpdump -nr<ENTER>".  To use it with open_with, you need to add
a line for tcpdump to rifle.conf.  Check the section about "rifle" in
the ranger man page and the documentation in rifle.conf.
but that is what I did.
but the problem is, I see the command output flushed away in front of my eyes, and disappears. I guess there must be a way to retain the the content...so looks that the '#' which puts a "-p" to pause (page) the shell outputs?

I'll check the rifle you mentioned for the open_with feature...I think that's another more useful way to look at the file in productions, instead of just a "quick" look, like the '#' or preview solution.

b.t.w, currently I have worked around it (without doing any magic in ranger rifle), with vim ,which took some autocmd to render the file with tcpdump cmds.. but the issue of that is, there is no easy way to change the tcpdump options in the fly --- I have to change the autocmd in my vimrc , reload vim and read the file again...


reply via email to

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