Re: NEW: x11/xcape

Hi Jon, Jon Bernard wrote on Fri, Jul 07, 2017 at 07:30:46AM -0400: > * Edd Barrett wrote: >> On Sun, Jul 02, 2017 at 04:38:49PM +0100, Edd Barrett wrote: >>> Fix up the above and send a new tarball and I will see if we can put >>> this in for you :) >> Oh, and if I were

Re: NEW: x11/xcape

On 2017/07/07 07:32, Jon Bernard wrote: > * Edd Barrett wrote: > > Hi Jon, > > > > On Tue, May 02, 2017 at 09:51:57AM -0400, Jon Bernard wrote: > > > This is my first port, I think everything is in order from what I've > > > read but do let me know if I've missed or

Re: NEW: x11/xcape

* Edd Barrett wrote: Hi Jon, On Tue, May 02, 2017 at 09:51:57AM -0400, Jon Bernard wrote: This is my first port, I think everything is in order from what I've read but do let me know if I've missed or misunderstood something. Here are a few comments: * You need to

Re: NEW: x11/xcape

* Edd Barrett wrote: On Sun, Jul 02, 2017 at 04:38:49PM +0100, Edd Barrett wrote: Fix up the above and send a new tarball and I will see if we can put this in for you :) Oh, and if I were nitpicking: $ mandoc -Tlint /usr/local/man/man1/xcape.1 mandoc:

Re: NEW: x11/xcape

* Edd Barrett wrote: Hi, On Mon, Jul 03, 2017 at 09:30:50AM +0200, Antoine Jacoutot wrote: > * Funny that they have an install target which installs the manual, but >not the binary! Doh! Might want to report that, so that in later >versions you don't need a

Re: NEW: x11/xcape

* Antoine Jacoutot wrote: On Sun, Jul 02, 2017 at 04:38:49PM +0100, Edd Barrett wrote: Hi Jon, On Tue, May 02, 2017 at 09:51:57AM -0400, Jon Bernard wrote: > This is my first port, I think everything is in order from what I've > read but do let me know if I've missed or

Re: NEW: x11/xcape

Hi Edd, Edd Barrett wrote on Mon, Jul 03, 2017 at 09:49:52AM +0100: > On Sun, Jul 02, 2017 at 07:33:19PM +0200, Ingo Schwarze wrote: >> Edd wrote: >>> But unless it breaks rendering, I wouldn't worry. >> I'm not aware of any way how that one could break rendering, >> so you certainly don't need

Re: NEW: x11/xcape

Hi, On Mon, Jul 03, 2017 at 09:30:50AM +0200, Antoine Jacoutot wrote: > > * Funny that they have an install target which installs the manual, but > >not the binary! Doh! Might want to report that, so that in later > >versions you don't need a custom do-install target. > > They do

Re: NEW: x11/xcape

On Sun, Jul 02, 2017 at 07:33:19PM +0200, Ingo Schwarze wrote: > > But unless it breaks rendering, I wouldn't worry. > > I'm not aware of any way how that one could break rendering, > so you certainly don't need to worry. Thanks for clearing that up Ingo. > So i should probably downgrade > >

Re: NEW: x11/xcape

On Sun, Jul 02, 2017 at 04:38:49PM +0100, Edd Barrett wrote: > Hi Jon, > > On Tue, May 02, 2017 at 09:51:57AM -0400, Jon Bernard wrote: > > This is my first port, I think everything is in order from what I've > > read but do let me know if I've missed or misunderstood something. > > Here are a

Re: NEW: x11/xcape

Hi Edd, Edd Barrett wrote on Sun, Jul 02, 2017 at 05:00:21PM +0100: > On Sun, Jul 02, 2017 at 04:38:49PM +0100, Edd Barrett wrote: >> Fix up the above and send a new tarball and I will see if we can put >> this in for you :) > Oh, and if I were nitpicking: > > $ mandoc -Tlint

Re: NEW: x11/xcape

On Sun, Jul 02, 2017 at 04:38:49PM +0100, Edd Barrett wrote: > Fix up the above and send a new tarball and I will see if we can put > this in for you :) Oh, and if I were nitpicking: $ mandoc -Tlint /usr/local/man/man1/xcape.1 mandoc: /usr/local/man/man1/xcape.1:31:57: WARNING: whitespace at

Re: NEW: x11/xcape

Hi Jon, On Tue, May 02, 2017 at 09:51:57AM -0400, Jon Bernard wrote: > This is my first port, I think everything is in order from what I've > read but do let me know if I've missed or misunderstood something. Here are a few comments: * You need to mark the port as not having tests (see

NEW: x11/xcape

Hi ports@, Attached is a port of xcape from Albin Olsson. DESCR: xcape allows you to use a modifier key as another key when pressed and released on its own. Note that it is slightly slower than pressing the original key, because the pressed event does not occur until the key is released. The