Expanding Spaces in Commands?

[Steve Holmes]

I can't see how or why Speakup would insert spaces when you type.  But
here's another thing you might try to use to substitute characters.
When getting ready to type the character you want quoted, type a
backslash (\) before it.  Ampersands are a bad thing to work with
because if unquoted, they could cause the previously typed stuff to be
treated as a command to be forced into background and then you would
lose track of it.  If it was a partial command, then it would probably
error out somewhat harmlessly.

HTH.

On Wed, Oct 06, 2010 at 11:48:33AM -0700, Hart Larry wrote:
> Hi All:  Right this second I cannot remember exactly what we were
> trying to configure, but my friend wanted me typing commands with
> ampersnds, so ofcourse I realized I needed quote signs.  Well, even
> with that, seemingly either tcsh or Speakup inserted spaces where I
> didn't type or want them.  We then used screen-and-he did the
> typing, obviously without Speakup, and it completed fine.
> Is this space expansion something I can turn off in FC9?  Even if I
> arrow up-and-delete those spaces, they come back again, once I hit
> enter.
> In screen, since it was his session, we were in bash, but I sure
> prefer running in tcsh, as all my aliases work, unelss maybe, are
> their ways to make global aliases, not specific shell dependant?
> Thanks so much in advance
> Hart
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup