[MacPorts] #13668: Selfupdate breaks keyboard handling
#13668: Selfupdate breaks keyboard handling -----------------------------------------------+---------------------------- Reporter: Ryan.Stonecipher.Fisher@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.6.0 Keywords: | -----------------------------------------------+---------------------------- Self-updating from 1.5.2 to 1.6.0 causes the delete key to output "^H" and the tab key to insert whitespace. OS X 10.4.11 Xcode 2.4.1 -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13668> MacPorts </projects/macports> Ports system for Mac OS
#13668: Selfupdate breaks keyboard handling ------------------------------------------------+--------------------------- Reporter: Ryan.Stonecipher.Fisher@gmail.com | Owner: jberry@macports.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: ------------------------------------------------+--------------------------- Changes (by jmpp@macports.org): * owner: macports-tickets@lists.macosforge.org => jberry@macports.org * milestone: => MacPorts base bugs Old description:
Self-updating from 1.5.2 to 1.6.0 causes the delete key to output "^H" and the tab key to insert whitespace.
OS X 10.4.11 Xcode 2.4.1
New description: Self-updating from 1.5.2 to 1.6.0 causes the delete key to output `^H` and the tab key to insert whitespace. OS X 10.4.11 Xcode 2.4.1 Comment: I presume you mean running MacPorts in interactive mode. If so, a substantial change between 1.5.2 and 1.6.0 is that readline support was switched to off by default due to the sheer amount of compile time problems it caused, and not having such support would definitely explain the behavior you're seeing. Selfupdating preserves some settings across upgrades, but I don't think it has the ability to detect whether the installed MacPorts had readline support integrated and preserve it as appropriate. I'm assigning this ticket to James (interactive mode author) so that he can comment on the matter. In any case, one quick way to get readline support back in is to install MacPorts from source. Download [http://svn.macports.org/repository/macports/downloads/MacPorts-1.6.0/MacPort... the tarball] and configure the sources with the `--enable-readline` switch to the `configure` script. -jmpp -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13668#comment:1> MacPorts </projects/macports> Ports system for Mac OS
participants (1)
-
MacPorts