Re: [dev] dwm 6.4 bug

2022-10-26 Thread spaceman
NRK writes: > I had bought up this issue in the past and the conclusion was that there > should just be a comment added [0] as users are treated as programmers. > > [0]: https://lists.suckless.org/hackers/2208/18484.html > > - NRK > I should have read the archives before emailing. Thanks for the

Re: [dev] dwm 6.4 bug

2022-10-26 Thread Tom Schwindl
> I had bought up this issue in the past and the conclusion was that there > should just be a comment added [0] as users are treated as programmers. > > [0]: https://lists.suckless.org/hackers/2208/18484.html > So be it! :-) A user report is a good reason for adding the comment. -- Best Regards,

Re: [dev] dwm 6.4 bug

2022-10-26 Thread NRK
On Wed, Oct 26, 2022 at 02:10:19PM +, Tom Schwindl wrote: > However, a length check & truncation > of the last char doesn't seem harmful at all. Thoughts? I had bought up this issue in the past and the conclusion was that there should just be a comment added [0] as users are treated as

Re: [dev] dwm 6.4 bug

2022-10-26 Thread Tom Schwindl
Hi, On Tue Oct 25, 2022 at 5:03 PM CEST, spaceman wrote: > Hi, > > While compiling dwm on slackware 15 I get the following (with > _FORTIFY_SOURCE=3): And therein lies the catch. The call to strncpy(3) copies the symbol of the currently selected layout to the layout symbol (ltsymbol) which will

[dev] dwm 6.4 bug

2022-10-26 Thread spaceman
Hi, While compiling dwm on slackware 15 I get the following (with _FORTIFY_SOURCE=3): In file included from /usr/include/string.h:519, from dwm.c:29: In function 'strncpy', inlined from 'arrangemon' at dwm.c:400:2, inlined from 'arrange' at dwm.c:394:3, inlined from