freebsd what shell do you use?

just out of curiosity

tcsh because it comes installed by default. If I have the time, I install bash sometimes. The reason -- bash's auto file completion is a bit better than tcsh IMHO

Full ack!
The only reason I prefer bash over tcsh is the listing of all possible names on TAB-TAB and some other minor differences in behaviour I cannot think of right now.

Maybe also because I am used to bash from working with linux for years where it usually is the default shell.

...M

yeah. bash either my best one. I love it for tabs and this easyness of using. csh is not bad either, but .. bash rocks.

I grew very fond of David Korn's ksh when working on HP-UX a few years ago. Bash also seems to share a lot with korn, although I do miss the ability to set my prompt to work in vi mode.

</$0.02>
christo

BTW on OpenBSD, csh is the default shell for historical reasons, but sh is also installed by default. The nice thing on OpenBSD is that /bin/sh is actually ksh (i.e. the korn shell) which has the same autocomplete features as bash (i.e. the TAB TAB thingy).

Look what my MOTD told me a few minutes ago LOL:


...M

PS: Anybody successfully connected to an IRCnet server from behind a NAT router?

thanks for the tip manuel. As for the NAT router thingy, see if using a different port like 6668 or 6669 helps -- maybe someone is blocking port 6667 on your firewall and some IRC servers run on multiple ports

Thanks, got it

Needed to run a ident server because of my ISP, but my first choice (pidentd) was not NAT capable nor were my "paranoid" firewall settings LOL... sh1t happens. finally I made it

/me lubs his tcsh

I use csh/tcsh for interactive work, sh/bash for scripting.

I used to use Bash a lot in Linux, but since I installed BSD, I've just been using TCSH and have been pretty happy (I've got some issues I think are terminal related, like a functional numpad and delete keys). Couple things from my .cshrc that make life easier:

set promptchars='$#'
set prompt="%/ %# "
set autolist='ambiguous'

That last one makes the tab-complete business work more like bash's default. One tab to complete as much as is universally similar, another to show a list of possibilities.

edit1:
Was just looking into the delete key business, according to my trusty ascii table, it says it's octal 176. Unfortunately, that also seems to be the ~, which makes sense, as every time I hit del, it rings the bell and prints a ~. Punks, they're two different keys! Can't use 'bindkey "\176" delete-char' without killing the ~, too.

edit2:
Aha! I don't really understand how it works, but it does. This is going in the .cshrc:

bindkey '^[[3~' delete-char