Re: odds and ends

[Daniel J S. <dan...@ie...>]

Hans-Bernhard Br=F6ker wrote:
> Daniel J Sebald wrote:
>=20
>> I've probably asked this before, but preceding and trailing white
>> spaces... should those not be ignored as the code currently does?
>=20
>=20
>> gnuplot> load ' histograms.dem'
>>                                ^
>>          Cannot open load file ' histograms.dem'
>>          util.c: No such file or directory
>=20
>=20
>> gnuplot> load 'histograms.dem '
>>                                ^
>>          Cannot open load file 'histograms.dem '
>>          util.c: No such file or directory
>=20
>=20
> Erm... are you sure this question makes sense as written?
>=20
> No, leading and trailing whitespace inside strings should *not* be
> ignored. If the code currently does that, that's a bug.

You mean "currently doesn't do that", I think.  (I originally framed the =
issue as double negative, but so no other way.)

As far as strings are concerned, trailing white space should not be ignor=
ed.  But when it comes to the point of attempting to open a file, can the=
 trailing whitespace be ignored?...  Oo, I guess I should retract that.  =
I just attempted to open something in gvim and placed white space before =
and after the name.  gvim created a new file with spaces instead of openi=
ng the file I intended.

(Whoever came up with the idea of white space in computer file names?  Ev=
er list a directory with such files?  It's downright confusing.)


>> For the history readline, the Home key places an "OH" in the line and
>> the End key places an "OF" in the command line. =20
>=20
>=20
> There's an off chance you can fix that by turning of "application curso=
r=20
> keys" mode in your xterm.

I wondered about that.  I see some keyboard settings in my xterm, but not=
hing having to do with the end and home keys.  I'll investigate.

Dan