tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: Respect MACHINE.
Date: Wed, 14 Dec 2011 14:08:38 +0100	[thread overview]
Message-ID: <4EE89FD6.7040908@bsd.lv> (raw)
In-Reply-To: <20111214113647.GA29912@iris.usta.de>

>> The enclosed small patch respects the MACHINE variable
>
> I hate environment variables in general (as opposed to variables
> used inside programs, like those in daily(8) and security(8)).
> I think looking at them is a bad idea in most cases.
> They change behaviour of programs, and as a user,
> it is very easy to forget about variables one has set,
> and it may even happen that the administrator changes
> variables behind one's back (in /etc/profile).
>
> Whenever a program looks at a variable, it should be checked
> whether looking at the variable can be removed, and i'm OK with
> keeping it only when there are very strong reasons to do so.
>
> Adding new variables is almost never OK with me.
>
> Keeping MANPATH is probably OK because it has been around so
> long and many people are probably used to it; removing it would
> be likely to cause more confusion than continuing to support it.
> But adding to that - no, i hate the idea.
>
> Regarding MACHINE, i believe that variable should not be used at
> all except for technical purposes, like in build systems.
> It should not affect which documentation i can find!
> If i had a VAX, i would certainly often use apropos(1) on i386
> or amd64 to search for VAX documentation, just because it's
> faster, and i would not want to fiddle with the environment.
>
>> as stipulated in man(1).
>
> I fear in man(1), that may have to be kept, for historical reason,
> though i do think it's a bug that man -aw does not ignore MACHINE.
> Then again, unless it's stipulated by POSIX, maybe it should be
> removed completely.  Why would anybody tweak the shell to display
> manuals for the wrong architecture by *default*?  If i want to see
> one specific manual for a different architecture, i will use -S.
>
>> This isn't mentioned in apropos(1) or whatis(1),
>
> No, because such bloat is absent there, as it should.
>
>> but it makes sense to be consistent with man(1)'s environment
>> (MANPATH, etc.).  Thoughts?
>
> Please drop that patch, without replacement.

Hi Ingo,

Well!  I've no problems with dropping this, of course.  Just trying to 
keep the manpage tools consistent.  In my opinion, it should really be 
dropped from man(1) as well... it seems totally superfluous, no?

Thanks for the look!

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

      reply	other threads:[~2011-12-14 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 10:44 Kristaps Dzonsons
2011-12-14 11:36 ` Ingo Schwarze
2011-12-14 13:08   ` Kristaps Dzonsons [this message]

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=4EE89FD6.7040908@bsd.lv \
    --to=kristaps@bsd.lv \
    --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).