\h behaviour - strange ?

Frank G Hahn writes:

However the \h expects everything after \h to be exact (after the
initial space(s) ).

Yeah, that's probably a little dumb. Perhaps I can squeeze that into 7.0.1
or so.

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden

Seems this is fixed in 7.0.

Hi
Hope this is the correct mail-list for last-detail-bugs before release.
Just installed RC4.
Requested help on create function using \h using
tab-completion. Really nice feature btw.
However the \h expects everything after \h to be exact (after the initial
space(s) ).

The help-request below will return 'No help ...'
'\h CREATE FUNCTION ' <- Note ending space, result of tab-completion.

Would the preferred behaviour of \h not be white-space-stripping ?
(or rather ignoring white-spaces altogether)

Minor detail, but it's there.

doesn't accept
'\h create function'
either. (two spaces)

/Frank

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

On Tue, 13 Jun 2000, Bruce Momjian wrote:

Seems this is fixed in 7.0.

7.0.1

Hi
Hope this is the correct mail-list for last-detail-bugs before release.
Just installed RC4.
Requested help on create function using \h using
tab-completion. Really nice feature btw.
However the \h expects everything after \h to be exact (after the initial
space(s) ).

The help-request below will return 'No help ...'
'\h CREATE FUNCTION ' <- Note ending space, result of tab-completion.

Would the preferred behaviour of \h not be white-space-stripping ?
(or rather ignoring white-spaces altogether)

Minor detail, but it's there.

doesn't accept
'\h create function'
either. (two spaces)

/Frank

--
Peter Eisentraut Sernanders v�g 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden