1) They used OpenSUSE Build Service for RPMs YES. Why don't they also use the service for DEB?
2) I prefer ncurse to any gui ever. So much fast to use and read.
3) VIM bindings for the most part and the short cuts look very well thought out
4) Marking and copying gives the same feeling as Ranger File Manager which I use all the time and when forced to use Windows it is the first thing I always miss.
Great job and look forward to adding this to my common work flow with my Linux boxes.
While not exactly the same as lnav, at Mobile Jazz we're building a remote logger for mobile devices (iOS only at this stage, support for Android, JS web apps and native desktop applications coming soon): http://bugfender.com/
We use Bugfender already for our own applications as well as for our clients, but we'd love to hear some unbiased feedback from other people whether or not this would be a useful product worth paying for. You can sign up here for a free beta account: https://app.bugfender.com/signup
A quick try on ubuntu 12.04 64bit failed to compile(latest 0.7.2 release):
lnav-0.7.2/src/static-libs/libncurses.a(lib_mouse.o): In function `_nc_mouse_event':
(.text+0x61e): undefined reference to `Gpm_GetEvent'
lnav-0.7.2/src/static-libs/libncurses.a(lib_mouse.o): In function `enable_gpm_mouse':
(.text+0x78c): undefined reference to `Gpm_Close'
Then I did this to "fix" it:
./configure --disable-static
I am on MacOSX and interested but spoiled by debian.
How do I come by the dependencies mentioned: libpcre, sqlite, ncurses, readline,zlib, bz2?
brew install doesn't know the formula if I brew install libpcre.
Sorry for being a noob.
Any facility for piping, for example to route an adb logcat (live remote log tail from android) through it?
Of course, I could redirect the adb logcat output to a file and point this at that, but it'd be nice to have the sugar to not have to explicitly wrap the process.
You can pipe into lnav like you can with less/more:
make |& lnav
The '-t' option will prepend timestamps to the lines that are coming in on stdin so that it will be treated as a log file. The '-w <file>' option will write the stdin data to a file if you want to look at it later:
