Your message dated Sun, 18 Oct 2009 11:38:03 +0400
with message-id <[email protected]>
and subject line Re: Missing referand in man page expect(1)
has caused the Debian Bug report #510427,
regarding Missing referand in man page expect(1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
510427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510427
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: expect
Version: 5.43.0-17
Severity: minor
expect(1) refers to a note on "system indigestion", but that note
doesn't seem to appear anywhere in the man page.
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages expect depends on:
ii libc6 2.7-16 GNU C Library: Shared libraries
ii tcl8.4 8.4.19-2 Tcl (the Tool Command Language) v8
expect recommends no packages.
Versions of packages expect suggests:
pn expectk <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
Reuben Thomas <[email protected]> wrote on Thu, 01 Jan 2009 18:11:17 +0000
> expect(1) refers to a note on "system indigestion", but that note
> doesn't seem to appear anywhere in the man page.
The reference to a system indigestion was in the sentence where ^ and
$ regexp anchors behavior was explained. A simple search for "system
indigestion" reveals the following paragraph:
Even depending on line-oriented buffering is unwise. Not only
do programs rarely make promises about the
type of buffering they do, but system indigestion can break
output lines up so that lines break at seem-
ingly random places. Thus, if you can express the last few
characters of a prompt when writing patterns,
it is wise to do so.
It adds more info on why ^ and $ behave this way. So, I think that
this bugreport should be closed. And I'm closing it.
Cheers!
--
Sergei Golovan
--- End Message ---
