Are you not the least bit curious to understand why bash would do such a thing, or what the actual cause of the problem might be?

No. I may come back to this later, but right now I'd rather have a shell that just worked.

Edit: actually this is more interesting than I thought; I thought it was undocumented shell option behavior, but it did not go away when I reset the shell options to defaults. Scary. I had better look into it.

Thanks.

I have to admit it made me curious. Can you give an example of what is happening?

(EDIT: I see that you have opened a thread for this, will follow it there...)

======================

I suspect you just answered to question as to why bash is so popular.

I too used the DEC once upon a time. I found tcsh did not fit my thought processes. I ran the canned programs the company had on it and left it alone otherwise. Just like most people do with Window$. At a point in time I needed to go beyond what the programmers of a specialty of which they knew nothing of had provided. The UNIX on the DEC did not blow up as much as Window$. (These programs were directly responsible for the DEC problems, but could be "blown away" without killing the OS by simply killing the window they were in.) That lead me to researching Unix and Linux. I selected Linux because it fit my "work process" better. It came with a number of shells (front ends). I started with the old standard sh and soon found its limits. csh and others and my idea of how to proceed through a problem clashed. I tried bash and like you said, I tailored it to me and been using it since. It has some serious shortcomings but is 95% effective.

In looking through the comments I get the feeling most of those posting are actually not programmers. I also get the feeling most have not been shown any kind of creative processing process. Thus the lack of understanding of scripting uses. Being able to pilot a process through command line : GUI : command line : and so forth to completion by way of a script is what gives Linux it's power.

This really doesn't belong here but:
... forget the boxes, the lines, the arrows
... use the old fashion Term Paper Outline
... create the steps in a file as comments.
... fill in with the code.
Creating the Outline forces you to think it out. Logically.
and it is easy to follow.

Norseman01

my preferred login is cinnamon, it is v/well laid out user friendly better than windows obviously. I have used linux for 2decades just love this.

bash bash bash

It was a stray character in /etc/inputrc.

And I'm still sticking with mksh. It's great to have a shell that handles terminal resizes properly, instead of claiming to and failing like bash.

Stray characters have caused many weird behaviors (usually in ~/.inputrc). And so have intentional, but incorrect characters. I'm kind of scared to touch it.

It works on my machine, but I get two messages like this What might that mean?

You have to use the bind command: https://wiki.archlinux.org/index.php...ory_completion

1 members found this post helpful.

Ahh, yess. Works flawlessly. Thanks, TobiSGD .

ditto bash here.

bash. It does most of what I want. I just discovered vi mode, which is great because I'm on a vim kick.

I've been trying to get zsh working, but it seems borked on ubuntu, or maybe it's just borked in general. Still, the tab completion features are quite inspiring.

ksh seems like the unholy child of shell and a general purpose programming language. That's either great if you haven't discovered Python* and want to do everything in your shell's language. Given the choice, I'd rather keep the shell for wiring programs together and use a general purpose language for more complicated things like dealing with abstract data types, math and other things I can't wring out of the standard tools.

*sub in your language of choice here.

I use bash the vast majority of the time, I have used zsh in the past on a few occasions and I like its completion feature. At the moment I am trying to get more familiar with bash scripting as it's used everywhere and I'm trying to improve my scripts from being simply commands copy/pasted with minor if/else statements or cases. The syntax is really not what I am use to (python\java\c#) so it's a bit of a doozy.

I use bash mostly, and have been getting better at writing shell scripts in it.

My Raspberry Pi is running PiBang with no GUI, and it defaults to zsh. I've started playing with that and I like it. If I can get sufficiently up to speed with it on the RasPi, I will consider using zsh on my personal GNU/Linux systems.

I will leave bash on the production systems at work, though, as I'm not the only one who uses them.

________________________

Slackware 14.0 (CLI), Linux Mint 13 MATE, Windows 7, Windows XP, and Windows 2000 at work
Kubuntu 12.04.4 and Windows 7 dual-booting on the laptop
MEPIS 11.0 on the home desktop (soon to become Linux Mint 17 KDE) dual-booting with Windows 7
PiBang v.20131119 (CLI) on the Raspberry Pi old model B (256 MB RAM)