From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>
Subject: RE: Problems with cursor position and hotkey commands in nano v.4.3
Date: Thu, 26 Mar 2020 12:38:32 +0000 [thread overview]
Message-ID: <AM6PR03MB5282D3EB8B2E4E5F6A3FCBEBA4CF0@AM6PR03MB5282.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <AM6PR03MB5282AF3E49951697EACCA62BA4CF0@AM6PR03MB5282.eurprd03.prod.outlook.com>
>> Anybody else having problems with cursor position and hotkey commands in nano v.4.3?
Further to above, and a bit different:
I downloaded the current nano-4.9.tgz from source, extracted the source files and within Cygwin ran the
./configure .. .. make .. .. make install trio.
Perfect glich-free installation showing the new nano executable and support files located in /usr/local/bin/ and /usr/local/share/.
(NB the Cygwin-provided nano v.4.3 installation remains in place.)
The command
$ echo $PATH
returns
/home/user/bin:/usr/local/bin:/usr/X11R6/bin:/usr/bin:/sbin:/usr/sbin
(so /usr/local/bin/ precedes /usr/bin/ as required)
and the command
# which nano
returns
/usr/local/bin/nano
(as expected)
BUT: the command
$ nano --version
returns
GNU nano, version 4.3
which is not what is required, referring to the original and not the later installation; and the command
$ nano anynamedtextfile
reveals on screen that nano v.4.3 not v.4.9 is being used.
Q1 Am I doing / thinking / remembering something daft about command hierarchies, or should the expected v.4.9 be the one obtained (which it isn't)?
Q2 Should I _necessarily_ uninstall the original v.4.3 - and if so, why, given the expected priority usages?
Thank you!
next prev parent reply other threads:[~2020-03-26 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 12:06 Fergus Daly
2020-03-26 12:38 ` Fergus Daly [this message]
2020-03-26 16:07 ` Brian Inglis
2020-03-27 9:24 ` Fergus Daly
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=AM6PR03MB5282D3EB8B2E4E5F6A3FCBEBA4CF0@AM6PR03MB5282.eurprd03.prod.outlook.com \
--to=fergusd84@outlook.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).