tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Ingo Schwarze <schwarze@usta.de>
Cc: openssh-unix-dev@mindrot.org, tech@mdocml.bsd.lv
Subject: Re: Fwd: Small fixes for ssh.1 and ssh_config.5, OpenSSH_7.2p2
Date: Thu, 31 Mar 2016 21:24:57 +0200	[thread overview]
Message-ID: <20160331192457.grb_VWxTg%steffen@sdaoden.eu> (raw)
In-Reply-To: <20160331173846.GH22000@athene.usta.de>

Hallo Ingo, list,

Ingo Schwarze <schwarze@usta.de> wrote:
 |Steffen Nurpmeso wrote on Thu, Mar 31, 2016 at 07:11:14PM +0200:
 |> I still haven't checked the OpenBSD version of OpenSSH, but i have
 |> seen your message on their ML (via Gmane) and there you correctly
 |> state what \& is far, it is used to avoid (mis)interpretation of "!".
 |> So it should be before that, not thereafter.
 |
 |Non sequitur.

So now i have, and the bug(s) is (are) still in there.  It is
a bug, if i type "man ssh_config" i see

       PermitLocalCommand
              Allow  local  command  execution  via the LocalCommand option or
              using the ! Ns command escape sequence in ssh(1).  The  argument
              must be ``yes'' or ``no''.  The default is ``no''.

In OpenBSD language that is total crap.
If i type "zcat /usr/share/man/man5/ssh_config.5.gz|mandoc|v"
i see ... the very same!

 |In many languages, you escape characters by placing something before
 |them.  But that isn't true in roff.  In some contexts of roff, you can
 |escape stuff by putting something *after* it.
 |
 |>>> and that mandoc falsely does the correct thing, if that is possible.
 |>> Mandoc correctly does the correct thing.
 |> The CVS version now does.
 |
 |Now you confuse me completely.  During the last few years, i changed
 |nothing in the mandoc code we are talking about.  So how can the
 |version of mandoc matter?

The version from September 2015 acted as if "\&! Ns" had been
used.  I don't have it no more, and am toooo lazy to bite.
In the meanwhile i seem to remember a message from A. J. Bentley
who reported some bug a while back, did he?  I'm drowning in work,
i'd surely search otherwise.

 |>> some people find it more intuitive to put the "\&" afterwards to
 |>> express that the character is not ending a sentence (i.e. is not a
 |>> delimiter).
 |
 |> A bug.
 |
 |No, that practice is just fine.
 |I don't understand why you keep calling it a bug.

Bugbugbugbugbugbugbugbugbugbugbug.
(Manually typed.)

 |> The visible flyspeck in the manuals of the portable version
 |> springs into the eye and drives you up the wall.  Bah.
 |
 |I have no idea what you are talking about.  Which formatter are you
 |using?  Which output does it generate for which input?

Just feeding animals in the zoo.  And then home.
Tschüß.

--steffen
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2016-03-31 19:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 19:25 Steffen Nurpmeso
2016-03-29 19:44 ` Steffen Nurpmeso
2016-03-30  9:26   ` Steffen Nurpmeso
2016-03-31 16:24     ` Ingo Schwarze
2016-03-31 17:16       ` Steffen Nurpmeso
2016-03-31 16:20 ` Ingo Schwarze
2016-03-31 17:11   ` Steffen Nurpmeso
2016-03-31 17:38     ` Ingo Schwarze
2016-03-31 19:24       ` Steffen Nurpmeso [this message]
2016-03-31 20:04         ` hans
2016-04-01 12:46           ` Steffen Nurpmeso
2016-04-01 12:53             ` hans

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

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

  git send-email \
    --in-reply-to=20160331192457.grb_VWxTg%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --cc=openssh-unix-dev@mindrot.org \
    --cc=schwarze@usta.de \
    --cc=tech@mdocml.bsd.lv \
    /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.
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 NNTP newsgroup(s).