From owner-freebsd-questions@FreeBSD.ORG Tue Jun 25 10:19:42 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0B8915AA for ; Tue, 25 Jun 2013 10:19:42 +0000 (UTC) (envelope-from aymeric@kuri.mu) Received: from borok.kuri.mu (borok.kuri.mu [193.170.194.196]) by mx1.freebsd.org (Postfix) with ESMTP id C5C5A1010 for ; Tue, 25 Jun 2013 10:19:41 +0000 (UTC) Received: from treefort.hro.nl (unknown [145.24.15.85]) by borok.kuri.mu (Postfix) with ESMTPSA id 08DEAE007D; Tue, 25 Jun 2013 12:30:19 +0200 (CEST) Date: Tue, 25 Jun 2013 12:19:28 +0200 From: Aymeric Mansoux To: Shane Ambler , Mark Felder Subject: Re: When to submit regression in a PR Message-ID: <20130625101928.GA1804@treefort.hro.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1371931585.12063.140661247273837.65C9D1AA@webmail.messagingengine.com> <51C53689.4060005@ShaneWare.Biz> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 10:19:42 -0000 Hi, Shane Ambler said : > > My question therefore is: while I will mention these problems > > upstream, should I also make the PR? Contact the port maintainer > > directly? I understand it is not FreeBSD specific (same issue on > > Debian Sid) however it really make the current port unusable for > > those working on laptops and those needing to input characters only > > reachable with the compose key. > > I would. While the ports are handled separately from the base system > they need to be maintained as well. If a version of a port has issues > then an older version could stay in place. > > The pr system is used for ports as well as the base system. Mark Felder said : > It's probably a good idea to open a PR and let the port maintainer > know, but we really need to have upstream to fix it. FreeBSD > discourages doing custom "development" in the ports tree, so even if > you could whip up a patch to fix it we would prefer that it get > committed upstream and the port updated to pull the new version rather > than have the port committer include a custom patch with the port. Thanks Shane and Mark. In fact, shortly after this mail a beginning of fix as been committed, so it will eventually surface in FreeBSD as well. Shane Ambler said: > Can't say I'm sure which key you refer to as compose - do you mean Alt > or Ctrl? I have heard of the ctrl key being remapped to the caps lock > for continuous use. You may also look into turning on sticky keys, it > keeps a modifier key active without holding it down so that the next key > pressed has the modifier included. see x11/xkbset You can turn any key into a compose/multi key. Mine is mapped on the Right Alt: setxkbmap -option compose:ralt It allows you to input characters such "é" or "ø" on keyboards where such keys are missing. It works by making key combos or chords. As for the stickiness of the key this is partly a problem linked to the fix just committed. By default a compose key seems to work both as sticky and non sticky to accommodate different writing styles/needs. This is noticeable in any X applications that accept keyboard input, from terminals to a browser. The last commit in upstream plan9port has brought back the functionality of the compose key only as sticky. When a key chord is done (non-sticky) the compose functionality is not working. Anyway this discussion is not so relevant to this list anymore :) Thanks again for advising on the PR issue! Very useful. Best, a. -- http://su.kuri.mu