Re: [dev] Looking for irc client

On Mon, May 18, 2020 at 10:03:35PM +0100, Dave Woodfall wrote: > You don't need SASL to use freenode. It does simplify > identifying/login, but it's not compulsory, unless you want to use > Tor. It's worth noting that Freenode does mandate SASL for certain IP address ranges known to be

Re: [dev] [slock] FDO lock event signal

On Sat, May 09, 2020 at 09:51:25PM +0200, Nicolo' Piazzalunga wrote: > With dwm and slock on Arch Linux, my password manager (keepassxc) does > not lock when I lock my screen (while it does when I suspend). > At keepassxreboot/keepassxc github (issue 4712), they say it might be > due to slock not

Re: [dev] [surf] Cannot copy URL to clipboard

On Wed, Mar 04, 2020 at 04:27:38PM -0500, Jason Blocklove wrote: > I've just reinstalled surf from scratch and everything seems to work as > expected so far except that I can't seem to use to copy the > current page's URL. I've tried both with the primary selection as well > as the clipboard

Re: [dev] Suckless/Simple version control

On Mon, Dec 09, 2019 at 10:42:09AM +0100, Kurt Van Dijck wrote: > On ma, 09 dec 2019 21:22:05 +1300, David Phillips wrote: > > On Mon, Dec 09, 2019 at 05:47:42AM +, Jacob Louis Prosser wrote: > > > Hey all, > > > > > > I started working on m

Re: [dev] Suckless/Simple version control

On Mon, Dec 09, 2019 at 05:47:42AM +, Jacob Louis Prosser wrote: > Hey all, > > I started working on my own version control system working with patch/diff. > Each commit is just a patch changing the last commit's files to the new ones. > It is currently implemented as a collection of shell

Re: [dev] [dwm] background wallpaper redraw

On Mon, Apr 22, 2019 at 10:52:32AM +0300, Dennis Yurichev wrote: > Hi all. > > When switching workplace to a free one, wallpaper doesn't show up.. > Is it known issue? > How are you setting the wallpaper in the first place? This may explain why dwm isn't drawing it. Thanks, David

Re: [dev] [slock] Need help working on the project

On Sat, Apr 13, 2019 at 07:57:23PM +0600, Enan Ajmain wrote: > Hi, > > I wanted to try and add a background image to the slock utility. I > have not worked on a project which needs "sudo" privilege. And now I > can't figure out how to work on this. For now, I am doing the > following. > > ``` >

Re: [dev] minimize window

On Sun, Jul 01, 2018 at 02:23:59PM +0800, Fei Teng wrote: > Hi, developers, > > Are there any method to minimize (hide) a window in dwm? > > Thanks > Switch the currently active tags, or change the tags applied to the window in question. Thanks, David

Re: [dev] home and del key not working

On Sun, May 27, 2018 at 02:39:25AM +0200, Salocin Ytchibrks wrote: > Del und Home Key dont work for me. I cloned ST from git. Patched it > with scrollback and clipboard. > Del Key Patch doesn't work. > > How can I solve this? > > Best regards > > Nic Have you read the FAQ file from the source

Re: [dev] [st] Text select and autoscroll

On Thu, Sep 14, 2017 at 10:26:56AM +0200, Rasmus Edgar wrote: > Hi, > > How do I get auto scroll (upwards and downwards) functionality when > selecting text which goes beyond terminal height? > > Br, > Rasmus st does not scroll

Re: [dev] st, spurious character in paste?

Sounds to me like you are accidentally rolling your scroll wheel. Thanks David

Re: [dev] [st, dmenu] Crash when attempting to display characters with missing glyphs

Related [1]? [1]: http://lists.suckless.org/dev/1610/30710.html

Re: [dev] [ANN] samurai: ninja-compatible build tool

On Wed, Jul 26, 2017 at 09:32:15AM -0700, Michael Forney wrote: > … Anyway, I'm a little suprised about the distaste for ninja since > it's features are pretty much the same as POSIX make (variable > assignments and rule definitions). I suppose the last half of that sentence outlines the distaste

Re: [dev] [surf] Errors compiling the surf-webkit2 branch

On Mon, May 29, 2017 at 03:29:47PM -0400, Albert Cardona wrote: > Hi all, > > Upon compiling the surf-webkit2 with either cc or clang, I am getting > a number of errors. I wonder if your config.h is outdated and is supposed to declare these. Not familiarvwith surf myself. Thanks.

Re: [dev] [st] Multiplexing support

On Sun, Apr 23, 2017 at 04:38:57PM +0200, Janne Heß wrote: > Hello everyone, > > While looking through the st TODO file, I found the task "add a simple > way to do multiplexing". > I was wondering what this is supposed to be? Something like > tabbing/tiling the terminal? And why do that? In my

Re: [dev][all] Migrating build system

On Sat, Apr 01, 2017 at 02:46:36PM +0530, Aditya Goturu wrote: > I am proposing we migrate to visual studio as our build system immediately. > We must also start reimplementing some parts in modern languages like C# or > Java. Have you seen FRIGN's efforts on porting sbase to Java [1] ? Perhaps

Re: [dev] [st] cannot disable antialiasing in 0.7

On Wed, Nov 16, 2016 at 06:02:47PM +0100, Hiltjo Posthuma wrote: > Can you bisect the offending commit? We expect some more work from you. > Especially when, speaking for myself, the problem cannot be reproduced. Additionally, it's probably a good idea to test against git HEAD in cases where it

Re: [dev] [dwm] crash on xsetroot emoji character

On Tue, Oct 25, 2016 at 12:43:34PM +0200, Petr Šabata wrote: > On Tue, Oct 25, 2016 at 11:36:49PM +1300, David Phillips wrote: > > I'm getting massive déja-vu from this, I remember an issue on github for > > a similar problem—perhaps with another wm. Unfortunately, I cann

Re: [dev] [dwm] crash on xsetroot emoji character

I'm getting massive déja-vu from this, I remember an issue on github for a similar problem—perhaps with another wm. Unfortunately, I cannot remember. Perhaps someone can remind me Cheers

Re: [dev] [st] can't set reverse cursor

On Wed, Oct 19, 2016 at 08:55:31PM +0100, Cág wrote: > Hiltjo Posthuma wrote: > > > The warning is exactly like it says: "maybe uninitialized" (it is not). > > Gcc warnings can be very useful but can also often be ignored. > > But it compiles fine, no errors starting st, and I suppose this is >

Re: [dev] dev+unsubscr...@suckless.org

On Thu, Sep 15, 2016 at 10:05:46AM +0100, Joseph Graham wrote: > hey Hi > -- > Joseph Graham Remember that it's the address, not the subject that should be dev+unsubscribe. All the best

Re: [dev] which versions are dwm patches intended to apply to cleanly?

On Wed, Jun 15, 2016 at 10:24:00AM +0200, Kamil Cholewiński wrote: > On Wed, 15 Jun 2016, David Phillips <dbphillip...@gmail.com> wrote: > > Some people thought it was a good idea to use 6.1 to denote git head before > > 6.1 actually came out. This worked fine until the

Re: [dev] which versions are dwm patches intended to apply to cleanly?

Some people thought it was a good idea to use 6.1 to denote git head before 6.1 actually came out. This worked fine until they stopped maintaining their patches to apply against git head. Something should be done about the patches that no longer apply cleanly, however. signature.asc

Re: [dev] [slock] [PATCH] Ctrl-u now resets the input

On Wed, Jun 08, 2016 at 09:55:38AM +0200, Anselm R Garbe wrote: > Hi Troy, > > I'm not sure if this feature is really required. Typing a wrong > password can be corrected on second attempt anyways. > > What is the opinion of other users to this change? > > BR, > Anselm Personally speaking, I

Re: [dev] [sup] Bring the simple user privilege escalation tool back home?

I would like to see the bugs suckless's sup examined and fixed. Looking at the current state of our sup, it is already too featureful for me, so the bloat jaromil promises is a big no. This discussion caused me to evaluate sudo for myself. Needless to say, it would be nice to see sup fixed up so

Re: [dev] Re: [slock] red color on control keys?

On Wed, Apr 06, 2016 at 02:48:27PM +0200, Markus Teich wrote: > we already discussed this. There are two settings, one for the "normal" people > and one for the paranoid ones. The setting you propose is mostly the same as > the > paranoid one, but slightly less paranoid. Why should paranoid

Re: [dev] Re: [slock] red color on control keys?

On Tue, Apr 05, 2016 at 11:47:09AM +0200, Markus Teich wrote: > Frostyfrog wrote: > > So, I understand that the red background color is supposed to signify that > > someone tried to log into the machine, but does it really need to turn the > > screen red when I press a no-op key? > > Heyho, > >

Re: [dev] Re: [slock] red color on control keys?

On Mon, Apr 04, 2016 at 11:50:38PM -0600, Frostyfrog wrote: > So, I understand that the red background color is supposed to signify > that someone tried to log into the machine, but does it really need to > turn the screen red when I press a no-op key? I generally press the > control key to wake

Re: [dev] [PATCH] Fix vertical character alignment in some cases

On Mon, Mar 07, 2016 at 10:18:12PM +0100, Ton van den Heuvel wrote: > The y-position of a character found by asking fontconfig for a matching > font does not take the border pixels into account, resulting in a > slightly misaligned vertical position. > > Signed-off-by: Ton van den Heuvel

Re: [dev] [sbase][PATCH] Add factor(1)

I am largely unfamiliar with sbase's codebase, but I wonder what the rest of the community will think of using GMP in an sbase tool. signature.asc Description: PGP signature

[dev] [PATCH] [st] copyurl patch with corrected clipboard behaviour

Previous version of the patch incorrectly set sel.primary, issue fixed. The original implementation of this patch copied the URL to the PRIMARY clipboard. st has since changed its behaviour to align with the freedesktop standard [0] on the issue such that, in general, explicit copy+paste actions

[dev] [PATCH] [st] copyurl patch with corrected clipboard behaviour

The original implementation of this patch copied the URL to the PRIMARY clipboard. st has since changed its behaviour to align with the freedesktop standard [0] on the issue such that, in general, explicit copy+paste actions use CLIPBOARD while implicit (eg selection-based) copying will use

Re: [dev] [PATCH] [slock] React to key release rather than key press events

On Thu, Jan 28, 2016 at 03:48:55PM +0100, Markus Teich wrote: > FRIGN wrote: > > So we want the screen to turn red on key down. > > Heyho, > > another even more annoying example is: I actually type my password so fast, > the > key release events are sometimes in the wrong order. You can test it

[dev] [PATCH] [slock] React to key release rather than key press events

Previously, if failonclear was set to True and a modifier key (especially shift) was pressed and held in order to modify the next keypress, slock would detect that a keypress had been made, observe that the buffer was clear and set the screen to the failure colour. That behaviour is unwanted if

Re: [dev] [PATCH] [slock] React to key release rather than key press events

> Heyho David, Hi Markus > I don't think we should change the current behaviour. As already explained > there > are two different ways of operation: > > - The paranoid option / failonclear = true: > Here you will leave your screen green and will notice ANY fiddling with the > keyboard.

Re: [dev] [bug] slock gets red before submitting pass

On Wed, Jan 27, 2016 at 05:16:55PM +0100, FRIGN wrote: > On Wed, 27 Jan 2016 13:58:56 -0200 > Brad Luther wrote: > > Hey Brad, > > > I think I found a bug on slock. > > No this is not a bug. > > > If you're typing your password and gets a char wrong, you go and > >

Re: [dev] [bug] slock gets red before submitting pass

On Wed, Jan 27, 2016 at 11:31:04PM +0100, FRIGN wrote: > On Thu, 28 Jan 2016 11:26:48 +1300 > David Phillips <dbphillip...@gmail.com> wrote: > > Hey David, > > > You have reminded me, however, that one regret I have since implementing > > this behaviou

Re: [dev] [PATCH] Change an eprintf to a die to stop child from running its own slideshow

On Thu, Jan 14, 2016 at 09:47:37AM +, Dimitris Papastamos wrote: > On Thu, Jan 14, 2016 at 09:02:43PM +1300, David Phillips wrote: > > The child thread was created because execlp will not return if successful. > > The eprintf was placed after the call to execlp to

[dev] [PATCH] Change an eprintf to a die to stop child from running its own slideshow

The child thread was created because execlp will not return if successful. The eprintf was placed after the call to execlp to catch any error, but the child continued to return a (closed) fds[0], resulting in a second slideshow being run by the child. This commit fixes the issue by killing the

Re: [dev] surf(git) and sound

> It does not seem to be any option related with the sound in the config.mk Looks like you've had your first taste of the satirical hiro :)

Re: [dev] Re: [farbfeld] announce

I tried compressing with bzip2 and xz, (both set to maximum compression with -9). I know xz to be slower, but I have measured it to have the least bloat when fed random data to compress. With "clean" low-noise images, it would seem that bzip2 is out-performing xz markedly, hence your

[dev] Patch naming on the wiki [corrected list]

On 10/11/2015, David Phillips <dbphillip...@gmail.com> wrote: > Just wondering what the rest of the community reckons about an issue > that popped up briefly on IRC. > > I'll start with an example: some patches, for a long time, have been > named `dwm-6.1-fibwibble.diff

Re: [dev] dmenu segfaults when pressing control+enter without a selection

Greg Reagle wrote: > Just started to try to do so, and now I really understand why people hate > stylistic source code changes. :> Eric Pruitt wrote: > Bingo. I now have 15 patches I have to fix because someone decided they didn't like booleans or the location of the opening brace for function

Re: [dev] Patch naming on the wiki [corrected list]

Hi all, > The shortref can check the date anyway. I think it is best that the filename > to be simple It is a lot slower to grab the shortref and look its date up, rather than just reading a date. > And we put the date (and maybe size) after the file This would solve my above problem, but

Re: [dev] Patch naming on the wiki [corrected list]

> Use shortrefs for the filename, but use dates on the wikipage or at least > annotate the hyperlink with the date. I like this idea. Now that you say it, the only reason I would have wanted the date in there too was to be able to quickly check how old a patch was. But there is really no need

Re: [dev] [slock] [PATCH] Blank the screen with colour 0

I have found a similar patch [1] submitted to the list about a month before this one was. It does not fix the initial issue my patch set out to solve (i.e. blanking the screen to the correct colour) but its functionality is provided by my patch. Note that [1] does not show the failure colour when

Re: [dev] [sbase][patch] typedef new structs

I can sympathise with both sides of the argument, but I'm not convinced code readability and maintainability will be negatively affected. As far as I can see, it comes down to personal taste, which I understand is often the spark of debate at suckless. -- Four word witty remark

Re: [dev] [st] [PATCH] FAQ: fix wordingy

Out of interest, was this thread created anew on purpose? Did I miss the joke? Thanks -- Four word witty remark

Re: [dev] [sbase][patch] test: a little cleanup

Stupid question: What's wrong with using **argv? Is there some style issue I'm unaware of? Thanks On 05/03/2015, Evan Gates evan.ga...@gmail.com wrote: use arg.h change **argv to *argv[] change strcmp == 0 to !strcmp change NOTREACHED to not reached fix test to check if basename(argv0) == [

Re: [dev] [ANNOUNCE] abduco-0.3

Being the author of the initial patch, Marc has reminded me to submit any feedback I have on the abduco_force patch, which will supersede my contribution. I did initially think of using a -f option, but didn't think there would be a need for any other option to be forced. This is how I ended up

[dev] [slock] [PATCH] Blank the screen with colour 0

When started, slock doesn't blank the displays to colour 0 until a slock to realise the input buffer is empty (i.e. backspace is hit). As far as I can tell, this isn't the intended behaviour. This patch fixes this problem such that as soon as slock is started, the display is blanked to colour 0,

Re: [dev] [website] [proposal] Add suckless logo and minor style change

I'm not sure how you're reading ssuckless. The separation between the stylised 's' and 'suckless' is 400% of that of the letter spacing in 'suckless'. Coupled with the vast difference in font, the contrast created should be significant to separate the first 's' from the word 'suckless'. I

Re: [dev] [website] [proposal] Add suckless logo and minor style change

Images [1] and [2] are food for thought. Excuse my ugly sans serif fonts. A thin line has been inserted between the suckless logo and the page title in both images. In [2], the subtitle has been floated on the right to avoid cluttering the left hand side of the header. Like I said, just more food

Re: [dev] important message

[...] you guys are self righteous assholes Finally, someone acknowledges my self-righteousness! -- David Phillips GPG Key 0x7BF3D17D0884BF5B Fingerprint 2426 235A 7831 AA2F 56AF 4BC0 7BF3 D17D 0884 BF5B

[dev] [stali] What happened to stali?

it's been stalled first. Did the concept fall to pieces? Is there nobody keen? What happened? Cheers -- David Phillips GPG Key 0x7BF3D17D0884BF5B Fingerprint 2426 235A 7831 AA2F 56AF 4BC0 7BF3 D17D 0884 BF5B