On Sun, Apr 21, 2013 at 12:25:20AM -0700, Linda Walsh wrote:
> If I 'reedit my last "statement", it indents 8 spaces/tab.
What does this sentence mean? I am completely stumped. What is
the sequence of steps you are actually performing?
Greg Wooledge wrote:
> On Sun, Apr 21, 2013 at 12:25:20AM -0700, Linda Walsh wrote:
>> If I 'reedit my last "statement", it indents 8 spaces/tab.
>
> What does this sentence mean? I am completely stumped. What is
> the sequence of steps you are actually performing?
---
Type in this:
echo 'whil
On Mon, Apr 22, 2013 at 10:54:35AM -0700, Linda Walsh wrote:
> Type in this:
> echo 'while read fn;do
> d=${fn%.zip}
This is where I lose you completely. If I press Tab where you indicate,
nothing happens at all.
If I press Tab twice in a row there, bash offers to tab-complete against
all the fi
Greg Wooledge wrote:
> On Mon, Apr 22, 2013 at 10:54:35AM -0700, Linda Walsh wrote:
>> Type in this:
>> echo 'while read fn;do
>> d=${fn%.zip}
>
> This is where I lose you completely. If I press Tab where you indicate,
> nothing happens at all.
---
But that is an empty line -- TAB 'should' be i
p.s. -- sorry for double post... but the fact that bad-design trumps
user usage steams me.
> Greg Wooledge wrote:
>> On Mon, Apr 22, 2013 at 10:54:35AM -0700, Linda Walsh wrote:
>>> Type in this:
>>> echo 'while read fn;do
>>> d=${fn%.zip}
>> This is where I lose you completely. If I press Tab
Greg Wooledge wrote:
> Are you perhaps pressing Ctrl-V Tab? Or have you done funny things with
> readline bindings? Or are you editing .bash_history with a text editor
> and then re-invoking bash in order to artificially insert a command
> with literal tabs into the shell's history buffer?
---
On Mon, Apr 22, 2013 at 12:35:02PM -0700, Linda Walsh wrote:
> I.e. do whatever you do to insert a TAB there. for me, I press TAB,
> Others have to work around BASH's unwanted, 4.x behavior.
I am not able to reproduce your problem.
Here is what I did:
imadev:~$ echo 'x
y
z'
Which means
Greg Wooledge wrote:
>
> Which means I typed <'>
> <'> at the Bash prompt.
>
> Then I pressed(I use vi editing mode also).
>
> Inside vi(m), I verified that the stuff in front of the y is an actual
> Tab character.
---
The problem is not that it replaces with space in the user-
