Re: [dwm] Suckess Code Management
On Fri, Mar 13, 2009 at 3:19 PM, Amit Uttamchandani
So if you need to work on let's say around 5-6 source code files along
with constant references to external files such as pdf's, etc. you have
multiple tabs in a terminal or multiple shells open and use that to
navigate the file system? Also if you had to copy between files between
multiple directories...isn't there a lot of typing going on?
To answer your questions
1. All the source files would be open in emacs, likely split screen.
2. All pdf's would be open in different instances of xpdf in a stack of
windows to the side of emacs. Same for firefox, e-mail, etc if it relates to
coding.
3. I usually have a couple terminals open, for any number of reasons; and
navigate the filesystem with cd fTABscTAB, cd -, etc. Terminals are
good for more than just navigation since they can be running make, gdb,
tcpdump, git, etc...
4. To copy files, use cp mixed with ls, find, grep, xargs, and
bash commands when useful.
Example, $find ~/music | egrep -i 'beatles|nirvana' | grep -i 'mp3$' | xargs
-i mv -n {} ~/favorite_tunes
isn't there a lot of typing going on?
Er, not really. How much effort would it be to find and consolidate every
beatles and nirvana song in a huge directory structure via tuxcmd?
Re: [dwm] Suckess Code Management
How do suckless members code? How do they manage multiple files? Bug reports, etc? I'm very curious to hear how others respond so I might as well pitch in too; 1. Window Manager = dwm/wmii 2. File Manager = bash 3. Text Editor = emacs 4. Calendar/Todo = cal/emacs/email (Google's Calendar for sharing) 5. File search = locate/etags 6. VCS = git/hg 7. Email = mutt/gmail 8. Chat = irssi 9. Music = mocp 10. Terminal = urxvtc 11. Terminal manager = screen 12. Debugger = gdb/valgrind 13. Build = make The 90%+ of the above works on just about every kind of *nix.
Re: [dwm] Suckess Code Management
I am astounded by how many respondents regularly use file managers! Yeah, I'm starting to feel like I'm missing something here... Do file managers have some killer feature that the shells (bash/tcsh/zsh/etc) don't? For all the mutt users, I imagine most are doing (fetchmail - procmail - mutt) right? I'll also give a big thumbs up to bitlbee and rtorrent which I just ran across recently.
Re: [dwm] minimal communication
Just curious, what are the advantages of sic over irssi? On Sat, Mar 7, 2009 at 10:48 AM, Jeremy Jay dinkuma...@gmail.com wrote: I'll second bitlbee, although I still use it with irssi. I do need to try out sic sometime though... Jeremy On Sat 07 Mar 2009 - 01:40AM, Uriel wrote: Bitlbee is the only remotely sane jabber client i know of uriel On 3/7/09, Scytrin dai Kinthra scyt...@gmail.com wrote: I'm slowly migrating from irssi to sic for IRC conversations, setting up up a hotkey in dwm to popup dmenu, which feeds into sic. sic will be displayed in either the root window or a terminal. I'm still figuring out the IPC for this setup to work sanely. My question however, is anyone familiar with a jabber client similar to sic? I've looked at freetalk and mcabber. freetalk seems more CLI oriented, but I doesn't seem that piping friendly to me. mcabber uses ncurses as an interface, but already has a few howtos on sending notifications and data to text files, which means I can get notifications similar to sic. But I'd have to utilize the application itself rather than a dmenu pipe. Anyone? -- stadik.net
Re: [dwm] xgamma notify
urxvt seems to ignore xgamma. So although it's a great idea, it isn't much help if you only have some terminals open. On Fri, Mar 6, 2009 at 9:05 AM, pancake panc...@youterm.com wrote: Samuel Baldwin wrote: 2009/3/6 pancake panc...@youterm.com: I have been playing a bit with xgamma and I think it can be useful as a graphical notification for important alerts like low battery or so. The usage is quite simple. and we can 'flash' the screen in red for a fraction of a second with: What happens if you're not looking at the screen? The screen explodes.
