on Thu, Dec 27, 2001 at 02:14:36AM +0100, Michael Mauch ([EMAIL PROTECTED])
wrote:
Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch ([EMAIL PROTECTED])
wrote:
Karsten M. Self wrote:
...
With gcc-2.95-doc installed, load time is ~1-2 seconds in Galeon
on Wed, Dec 26, 2001 at 08:10:46PM -0500, dman ([EMAIL PROTECTED]) wrote:
On Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch wrote:
| ((X)Emacs is everywhere).
Hmm,
$ dpkg -l \*emacs\* | grep ^ii
$
I think I just found nowhere :-).
...but are you in the _middle_ of it. That's
On Wed, Dec 26, 2001 at 01:48:55PM -0800, Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 02:29:19PM -0600, Colin Watson
([EMAIL PROTECTED]) wrote:
Ugh, yes, that's horrible formatting. '.nf' means no-fill mode, but it
has the effect you're thinking of. Make sure you add this line to the
On Tue, 25 Dec 2001 17:24:26 +0100, Imre Vida
[EMAIL PROTECTED] wrote:
As far as info is concerned, i fully agree with Karsten.
It doesn't work intuitively for me either; i just get
lost in the maze of links and 3 sentence pages
I hate it for this.
Use pinfo. Feels like lynx. Much more
On Tue, Dec 25, 2001 at 03:02:25PM -0800, Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 12:51:09PM -0600, Colin Watson
([EMAIL PROTECTED]) wrote:
Come up with examples and send patches. That'll achieve results much
faster than anything else I can think of.
Specific instructions on how to
Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 06:32:31PM -0800, Craig Dickson ([EMAIL PROTECTED])
wrote:
Carl Fink wrote:
BTW, for HTML docs, put them all in *one* file with hyperlinks. There is
no
meaningful advantage to cutting it into twenty pieces, and it makes
on Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch ([EMAIL PROTECTED])
wrote:
Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 06:32:31PM -0800, Craig Dickson ([EMAIL PROTECTED])
wrote:
Carl Fink wrote:
BTW, for HTML docs, put them all in *one* file with hyperlinks.
on Wed, Dec 26, 2001 at 03:38:20PM +, Colin Watson ([EMAIL PROTECTED])
wrote:
On Tue, Dec 25, 2001 at 03:02:25PM -0800, Karsten M. Self wrote:
on Tue, Dec 25, 2001 at 12:51:09PM -0600, Colin Watson
([EMAIL PROTECTED]) wrote:
Come up with examples and send patches. That'll achieve
Karsten M. Self writes:
My concern was whether or not I should post my revised manpage to the
bugtracking system itself.
You should.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
On Wed, Dec 26, 2001 at 10:59:58AM -0800, Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 03:38:20PM +, Colin Watson
([EMAIL PROTECTED]) wrote:
Do use the bug tracking system. In the case of printcap(5), a bug
should be filed against the three packages that contain it (lpr,
lprng,
On Wed, Dec 26, 2001 at 10:52:33AM -0800, Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch
([EMAIL PROTECTED]) wrote:
I think a decent search facility is a must for more in-depth
documentation. If I _know_ that I want to use newwin(3), I can easily
type man
on Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch ([EMAIL PROTECTED])
wrote:
Karsten M. Self wrote:
...
This can be further mitigated by browsers that render on partial
load, or which allow background loading of pages (Galeon rocks for
this).
Sorry, I disagree. Try
info
on Wed, Dec 26, 2001 at 02:29:19PM -0600, Colin Watson ([EMAIL PROTECTED])
wrote:
On Wed, Dec 26, 2001 at 10:59:58AM -0800, Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 03:38:20PM +, Colin Watson
([EMAIL PROTECTED]) wrote:
Do use the bug tracking system. In the case of printcap(5),
On Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch wrote:
| You might argue that I should use w3m or links to read those large HTML
| files - but then I would have to remember the keystrokes of these
| programs (i.e. I can't use my favourite browser) and I have to
| install/build these
Karsten M. Self wrote:
on Wed, Dec 26, 2001 at 04:31:12PM +0100, Michael Mauch ([EMAIL PROTECTED])
wrote:
Karsten M. Self wrote:
This can be further mitigated by browsers that render on partial
load, or which allow background loading of pages (Galeon rocks for
this).
Sorry, I
On Thu, Dec 27, 2001 at 02:14:36AM +0100, Michael Mauch wrote:
| Galeon 1.0 from the Debian system really is a lot faster (2 seconds
| for the whole file). So maybe something went wrong with my
| Galeon-0.12.7 build here (built from sources on something that once
| was a SuSE-6.1).
Ok, so galeon
On Tue, Dec 25, 2001 at 05:24:26PM +0100, Imre Vida wrote:
The lack of manpages, and outdated manpages are frustrating.
And what Karsten brought up is also a nice idea:
to have examples in man pages. There are some manpages with examples
but most of them are without although they are really
Imre == Imre Vida [EMAIL PROTECTED] writes:
Imre As far as info is concerned, i fully agree with Karsten. It
Imre doesn't work intuitively for me either; i just get lost in
Imre the maze of links and 3 sentence pages I hate it for
Imre this.
It's not man versus info -
* Imre Vida ([EMAIL PROTECTED]) spake thusly:
hi,
i just read the (sub)thread above on man v. info
and i thought it is much more important than
to have it hidden in there. So i thought i try
to pick it up again.
The major sources of help/information for me are
the apropos, the
on Tue, Dec 25, 2001 at 12:51:09PM -0600, Colin Watson ([EMAIL PROTECTED])
wrote:
On Tue, Dec 25, 2001 at 05:24:26PM +0100, Imre Vida wrote:
The lack of manpages, and outdated manpages are frustrating.
And what Karsten brought up is also a nice idea:
to have examples in man pages. There
On 25-Dec-01 Imre Vida wrote:
[snip]
The major sources of help/information for me are
the apropos, the -h/--help options and the man pages.
These are fast and efficient means to find what i want
most of the time.
As far as info is concerned, i fully agree with Karsten.
It doesn't work
On Tue, Dec 25, 2001 at 05:00:36PM -, Ted Harding wrote:
As to what to do about it, I can only suggest
reinstate the man pages in full. I know it's
not 'kosher' to disagreee with the GNU info
policy, but I think that those who do disagree
should say so. After all, it'a a Free and Open
Carl Fink wrote:
BTW, for HTML docs, put them all in *one* file with hyperlinks. There is no
meaningful advantage to cutting it into twenty pieces, and it makes
searching significantly more difficult.
For locally-stored docs that's arguable. The advantage of small files
comes when you have
on Tue, Dec 25, 2001 at 06:32:31PM -0800, Craig Dickson ([EMAIL PROTECTED])
wrote:
Carl Fink wrote:
BTW, for HTML docs, put them all in *one* file with hyperlinks. There is no
meaningful advantage to cutting it into twenty pieces, and it makes
searching significantly more difficult.
On Tue, 25 Dec 2001 [EMAIL PROTECTED] wrote:
I really agree with this. I find 'info' very frustrating;
[...]
As to what to do about it, I can only suggest
reinstate the man pages in full. I know it's
not 'kosher' to disagreee with the GNU info
policy, but I think that those who do disagree
On Sun, Sep 02, 2001 at 11:54:09PM -0400, Brian Nelson wrote:
I also agree. I think what bothers me most about info pages is that
they often read like books. They're usually arranged in a format
resembling chapters covering each topic in thorough detail. This is
fine if I want to read a
Brian Nelson wrote:
I also agree. I think what bothers me most about info pages is that
they often read like books.
Not suprising, they often *are* books. I have a book on my shelf that
has about a 100% correspondence to the gdb info page. Though the gdb
info page lacks RPM's autograph..
--
On Sun, Sep 02, 2001 at 03:13:10PM -0700, Karsten M. Self wrote:
on Sun, Sep 02, 2001 at 01:44:45PM +0200, Cliff Sarginson ([EMAIL PROTECTED])
wrote:
On Sun, Sep 02, 2001 at 11:49:11AM +0100, Colin Watson wrote:
On Sat, Sep 01, 2001 at 10:31:47PM +0800, Rino Mardo wrote:
regretful snip
I
wow. ever thought of getting into law practice? :-)
i think i touched on a very touchy issue here. i'll just go find a simple
project for my python.
thanks for all the replies guys!
_
Do You Yahoo!?
Get your free @yahoo.com address at
On Sun, Sep 02, 2001 at 03:13:10PM -0700, Karsten M. Self wrote:
Personally, I'd strongly recommend that the GNU project revisit the
issue of info pages altogether. They're not popular, they don't
adequately replace man pages, and there is a far more successful and
ubiquitous hypertext model
Karsten M. Self kmself@ix.netcom.com writes:
The problem is that this is often specifically what is *not* sought by
those who are looking for manpages. What's wanted is a short, concise,
but illustrative reference providing:
- A functional description of the command.
- A synopsis of
31 matches
Mail list logo
