From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.bugs Subject: bug#57556: 28.1; Eshell not finding executables in PATH when tramp-integration loaded Date: Sat, 15 Oct 2022 12:38:05 +0200 Message-ID: <87k051v0c2.fsf@gmx.de> References: <87h715j5gy.fsf@gmx.de> <0480c49e-75da-68c4-d255-242ff65323fe@gmail.com> <87czbsjyby.fsf@gmx.de> <877d1vthto.fsf@gmx.de> <871qrrffzj.fsf@gmx.de> <2d1f17a5-554d-1b1f-7bcb-52e3839d9d0c@gmail.com> <87wn9iehl1.fsf@gmx.de> <00448968-481d-9bdd-b0c8-7bc3d04e5d60@gmail.com> <87fsfzh4if.fsf@gmx.de> <67159bc7-b50c-ed93-ae3e-154b240b9eb7@gmail.com> <87o7ukdggp.fsf@gmx.de> <10e3d9b6-1fd5-c35f-625b-6dc02aa7de57@gmail.com> <878rlizj23.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24984"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 57556@debbugs.gnu.org To: Jim Porter Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Oct 15 12:39:34 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ojeZq-0006Lq-CT for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 15 Oct 2022 12:39:34 +0200 Original-Received: from localhost ([::1]:43932 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ojeZo-0004tn-VU for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 15 Oct 2022 06:39:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48982) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ojeZK-0004tG-6w for bug-gnu-emacs@gnu.org; Sat, 15 Oct 2022 06:39:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40517) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ojeZJ-0000vX-St for bug-gnu-emacs@gnu.org; Sat, 15 Oct 2022 06:39:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ojeZJ-00063o-O9 for bug-gnu-emacs@gnu.org; Sat, 15 Oct 2022 06:39:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Albinus Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 15 Oct 2022 10:39:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57556 X-GNU-PR-Package: emacs Original-Received: via spool by 57556-submit@debbugs.gnu.org id=B57556.166583029923235 (code B ref 57556); Sat, 15 Oct 2022 10:39:01 +0000 Original-Received: (at 57556) by debbugs.gnu.org; 15 Oct 2022 10:38:19 +0000 Original-Received: from localhost ([127.0.0.1]:39595 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ojeYc-00062h-S7 for submit@debbugs.gnu.org; Sat, 15 Oct 2022 06:38:19 -0400 Original-Received: from mout.gmx.net ([212.227.15.15]:46831) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ojeYb-00062T-0K for 57556@debbugs.gnu.org; Sat, 15 Oct 2022 06:38:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1665830288; bh=ws1DO1Uq4LKl16yOWAEd0vkRZU9WA/iDnrLyvjIaAsc=; h=X-UI-Sender-Class:From:To:Cc:Subject:In-Reply-To:References:Date; b=eQfuatjXPsqR+IJ7ZVl7753H4sERnsZ+yhmAFERhBbBTT7XFEJwIUtbeBJ8jy5r22 swfL9GU5QKEaQKVJXcZV2dgdju3D1YeM6INqNgB6gKSzga3ZTQGhfi5zrMysNUphvz PiowmbMyLEhlHfe9cI/nCpnAx46jXLlRxWRUuCQ4= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from gandalf.gmx.de ([213.220.151.229]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MZktZ-1ogCCV0hWB-00Wo0f; Sat, 15 Oct 2022 12:38:08 +0200 In-Reply-To: (Jim Porter's message of "Fri, 14 Oct 2022 13:53:33 -0700") X-Provags-ID: V03:K1:SFSNtJn1wEJ9uCLAO+aayJQ3mkr6WlxW4XlVlcE3vh0F+OK+HOM 26KOP+OEjFZWJ8kquJX6SCKKxMxuP4AIB/FMDnzBd9rl6GLT077Qu5Ck/Ip7fMnsv5wuA3s TS25evKlp5lyh0EpuTp5lv1vQtKcANg80jw1gob6Nm/WomDa6I9US7wW/AoX6fifZ/yZEDx Pnjhw40IS1ZDBGuIYwuMw== X-UI-Out-Filterresults: notjunk:1;V03:K0:h44+D8G8JfI=:snTkeGU9dU4S8pXTk5cixI Bl9GpDSC6baZxtvWbH85FpFU8CE41ir1fdsW5DrgUwrg7JV1Pz2hxxSsH3byxlST3iXy+cjUl QvnXgLA+OeabOzgQtc4rRMMz5aSiN7YIkvUyRJol0OKjsOZ85Vz3OSB2KwMJs90pPpGEeT6l1 IAawAReH+BZwPJNtbTbt5inyoIC5uu6/73M3CmwtpSK6WhSwRun48v2p25+rgi5uvWa7EmpsJ S+A0Vtys+yYf9yT5uJ4g8KpJ0HnTnPBlC9CdWsMRb25D3XYFzkm61aJKVN9RTtoxCKmGpxVX0 8LrX8UH5Tzocn04Cvann1JxqrFlF42uZr8qRoiHUcoCPdEJOrHHxgmyKC0CyKQnosUNjBPz27 b9FRguZCeG7fOo2PQBz70wLXG+WL2e3CtFbE3lDD4DhbKLxSQU3z3GDMScWOoGr7BEygolRRe TkgG3oHCQSUY9Itmn0R4AIuDL0LrGVhR4jZMgMnJqcZcvj4q3cCle/j5VF9ol8Dpy+vFIxH0f IlIvwNptP5hXlWmW1SMDQm3ESpLSWQ0TEDpNNAknBLLKn/zqdZn6j4x0L/ESrMOOp0jkM3kq6 ocH1NGuf/XThlQ7HJy3u5TjiLFrEEovNEdnU8BKB9a9zGX70tCJKl3eNlZnwb5MbK/4G48VTa entVLDHopEILejegsx9gKWKZz4fdi6gS70hOCbzZniXI6TSOzQz1pXT5NqL5Bhyfs1N1mxprs 7x11VYYxwCV7Ufa2fQAamqLuSJzuw9b12sefgft7I0LlnJ489X008Uwhg7Y5W7ZGtR4Y0gFu X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:245538 Archived-At: Jim Porter writes: Hi Jim, >> @var{} produces already capital letters, so you are more consistent >> with >> @var{name}. > > My intent was to make that display as all-caps in the HTML > documentation as well. In that excerpt, 'NAME' should always be an > environment variable, so I used the capitalization conventions that > env vars usually use. 'name', on the other hand, could be a Lisp > variable or an env var. You use @var{} by side-effect6, which is always problematic. For example, RMS is looking for a replacement of the texinfo syntax for documentation, org syntax is a candidate. But whatever is chosen, an automatic conversion from .texinfo to . could be problematic then. Use what is offered by texinfo. Say for example --8<---------------cut here---------------start------------->8--- the @env{PATH} environment variable --8<---------------cut here---------------end--------------->8--- And in sample code, do not apply further formatting, but say it as you mean it --8<---------------cut here---------------start------------->8--- @samp{setq name value} @samp{export NAME=value} --8<---------------cut here---------------end--------------->8--- > I adjusted these docs a bit since they seemed unclear to me on a > second reading (see attached), but kept the all-caps NAME for env > vars. If you still think that's wrong, I'll change it to lower-case > before merging. Otherwise, it LGTM. Somewhere there is only one space after a dot (should be two spaces), but I didn't marked this during review, and now I'm too lazy to look for :-) I'd say just push it to the repo, and if there's something left to do we can stiil do it. Best regards, Michael.