[MacPorts] #58529: Port command, in interactive mode, doesn't load the editline config file
MacPorts
noreply at macports.org
Mon May 27 05:12:49 UTC 2019
#58529: Port command, in interactive mode, doesn't load the editline config file
----------------------------+--------------------
Reporter: SenileFelineS | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.5.4
Resolution: | Keywords:
Port: |
----------------------------+--------------------
Description changed by SenileFelineS:
Old description:
> See here for background:
> https://echelog.com/logs/browse/macports/1558908000
>
> In attempting to find out why {{{port}}}, when running as an interactive
> shell, maps the key combination {{{Fn}}}+{{{Delete}}} to the tilde
> character {{{~}}} instead of the forward-delete, it was realized that
> "Apple's libedit doesn't actually respect EDITRC", which should be found
> at {{{~/.editrc}}}.
New description:
See here for background:
https://echelog.com/logs/browse/macports/1558908000
The initial issue was that the key combination {{{Fn}}}+{{{Delete}}}
should forward-delete text in the command line while running {{{port}}}
interactively in the shell - however, it instead produces a tilde
character {{{~}}}. The attempt to fix this in {{{~/.editrc}}} was
unsuccessful. (per user jmroot)
In attempting to find out why {{{port}}} has this behavior, it was
realized that Apple's libedit doesn't actually respect the $EDITRC
environment variable. As a result, it only looks at the default
$HOME/.editrc, and because {{{port}}} mucks around with/alters $HOME, the
user's {{{~/.editrc}}} is not found. (per user apjanke)
--
--
Ticket URL: <https://trac.macports.org/ticket/58529#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list