From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4385 invoked by alias); 6 Aug 2017 06:37:58 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22791 Received: (qmail 18913 invoked by uid 1010); 6 Aug 2017 06:37:58 -0000 X-Qmail-Scanner-Diagnostics: from mail-wm0-f46.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(74.125.82.46):SA:0(-0.0/5.0):. Processed in 2.000596 secs); 06 Aug 2017 06:37:58 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: linux.tech.guy@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to; bh=A066/U6q8TYjlxbtwbUz0ONwcXmeEGXq1O3V6LRg9jQ=; b=q0B+K89/nGz3e5F1nZ01NEK5llBGF+WTx7a8DfNSmSXI/ZsUJdn3zOzhLuhqRA0fXC a9u2JeFxsWUgDGH4npvxBU40fdleJcU4zoGaxv0RHNPeDZuTqi1s6J6mD+Bm7tQabZLK 46u5jcrwCschFAxjq8zriRVhe5VlqgB8pzq1I3o6eFjBty4/JPzANiHgi7TOejhhT71+ draT7d6JCxzwSmZW4baGXNTAqgTo8uEkjdkTDByHMXaB1GvTwVj4pDgeKSpttzoE06c1 S4Yzpt76d7irEXd7NwLp+yerFmnK6VI7gjqLYWCiu3McqqVkWCrZfPcPi0IG5rHotL14 842Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=A066/U6q8TYjlxbtwbUz0ONwcXmeEGXq1O3V6LRg9jQ=; b=GzC4aQT+rHtZ8Q94cPKyExbBck5uNxZR8aQABMq8rU/rbg/a/UbCYcZWCDwGfuHkwc NkmU9SpOUGGiUSmIE9/w33u2BHLvRGKQaNrKzgt2laDAnE1WZ3f5awH1A4w9Lz5VXJq+ uJ+l1bBFGuYDDxvZjpWYrSwRZg3iFhN1oXhpIrsuzYBUhGDEEoUMaNqqjTQZlXJ9lkOv GAO2QHySKUT6E9CiJUoKeqYEI91QC0xgJfuJ5fdLkDt/63wT+yj0NOjLOKpKd5mGm1nw pPw+3AuK9pkLaajwzkqdT1szUx97PtxSzI5yPZYEtM1H+4zolJlEzZxVXr9v43EJJJ7b s/7A== X-Gm-Message-State: AIVw113PifomJuwkrEwpWEkFjFWECxGlOxqqM8BpAz/lUIx7ifJW2LXp Bwx+rw5VqyxcFLPHRJMNJ8m/TrlAMw== X-Received: by 10.80.131.135 with SMTP id 7mr7782708edi.35.1502001470992; Sat, 05 Aug 2017 23:37:50 -0700 (PDT) MIME-Version: 1.0 Reply-To: linuxtechguy@gmail.com In-Reply-To: References: <76131501981203@web60g.yandex.ru> From: Jim Date: Sun, 6 Aug 2017 01:37:50 -0500 Message-ID: Subject: Fwd: Does mandir get saved some place? To: zsh-users@zsh.org Content-Type: multipart/alternative; boundary="94eb2c0d99d22172dc05560ff861" --94eb2c0d99d22172dc05560ff861 Content-Type: text/plain; charset="UTF-8" ---------- Forwarded message ---------- From: Jim Date: Sun, Aug 6, 2017 at 1:29 AM Subject: Re: Does mandir get saved some place? To: "Nikolay Aleksandrovich Pavlov (ZyX)" Forgot to change address to go the list. Nikolay, On Sat, Aug 5, 2017 at 8:00 PM, Nikolay Aleksandrovich Pavlov (ZyX) < kp-pav@yandex.ru> wrote: > 03.08.2017, 18:03, "Jim" : > > > With the fact that the configure script has the option "mandir= dir>" > > I assumed(bad thing to do) that there would be an easy way to discover > > where the man pages were saved. If there is, so far I haven't found it. > My > > reasoning for this is, if I'm testing a particular build, I would like to > > have > > available the pages for that build if they exist. I assumed(I know) > > that is why "mandir" is there, to make this possible. > > > > Is there a variable of something else that can be accessed to tell > > someone where a particular zsh build saved the man pages? If not, > > would it be unreasonable to ask that a variable like "mandir" be set with > > the path to those man pages? This would make it so much easier to > > set MANPATH. For me it would even be better if zsh automatically > > added a path to them before the normal locations. I'm sure others > > would disagree. An option allowing such behaviour would allow a user > > to set this to meet there own needs. > > > You can probably use `zsh -fc 'printf "%s" $module_path[1]:h:h:h/share/man'`. > Should work fine as long as you are only setting single installation prefix > based on which other locations are computed and not other installation > locations explicitly. All versions I ever needed have `$module_path[1]` set > to something like `{prefix}/lib(64)?/zsh/$ZSH_VERSION`, so three `:h` are > there to get rid of `lib*`, `zsh` and `$ZSH_VERSION` components. > I had been playing around with something like that. It assumes that the man pages go into the traditional locations of either /usr/share/man or /usr/local/share/man depending on the prefix. The issue with this, from what I've seen, is if two versions are installed with the same prefix, the last version installed will overwrite the previous version's man pages. Each version can be given its on directory to store the man pages, by adding the option --mandir= when executing ./configure during the build. This means they will be in a non-standard location and the location would have to be added to MANPATH. The result of using --mandir in this way is the method used above will not give you the results you need to set MANPATH. It would appear that unlike modules, which has the "module_path" variable, there is no equivalent variable for mandir. If there is I haven't found it. It can be argued that zsh doesn't need to know where the man pages are located. But the command "man" does, which means that zsh has to set MANPATH correctly. It would simplify things if zsh could somehow return this information. Thanks for responding, Jim --94eb2c0d99d22172dc05560ff861--