unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 1/3] gnu: man-db: Pass --with-col to configure.
Date: Tue, 21 Jul 2015 11:06:16 -0400	[thread overview]
Message-ID: <CAJ=RwfZr6EVyP2RepXk1PVujyY=kxank1-cpM8vo-HCyBLBsoA@mail.gmail.com> (raw)
In-Reply-To: <87d1zlmuc6.fsf@gmail.com>

On Tue, Jul 21, 2015 at 10:57 AM, Alex Kost <alezost@gmail.com> wrote:
> Quote from "man man":
>
> --8<---------------cut here---------------start------------->8---
> Normally, when output is not being directed to a terminal (such as to a
> file or a pipe), formatting characters are discarded to make it easier
> to read the result without special tools.
> --8<---------------cut here---------------end--------------->8---
>
> However it does not happen with the current "man", as may be checked for
> example by evaluating the following in Emacs:
>
> (let ((buf (get-buffer-create "*man true*")))
>   (with-current-buffer buf
>     (call-process "man" nil t nil "true"))
>   (pop-to-buffer buf))
>
> As you can see there are escape sequences (such as "^[[1m") there, which
> shouldn't happen.  Configuring man-db "--with-col" fixes the issue (at
> least for me).
>
> BTW (a note for Ludovic), the current man behaviour "breaks" completions
> of many commands provided by "pcmpl-args" emacs package, because
> 'pcmpl-args-extract-argspecs-from-manpage' can't parse a man page to find
> completions.  For example, "sudo --<TAB>" (in shell-mode) doesn't complete
> anything.  After this patch it should work.

Nice catch.  LGTM!

- Dave

  reply	other threads:[~2015-07-21 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 14:57 [PATCH 1/3] gnu: man-db: Pass --with-col to configure Alex Kost
2015-07-21 15:06 ` Thompson, David [this message]
2015-07-21 15:21 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ=RwfZr6EVyP2RepXk1PVujyY=kxank1-cpM8vo-HCyBLBsoA@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).