Re: [dev] Suggestion for project idea/christmas hacking: sbase xargs -P and -0 support

2024-12-14 Thread Laslo Hunhold
On Sat, 14 Dec 2024 12:03:37 +0100 Marc Chantreux wrote: Dear Marc, > > For example, I used it in my toy musl/Linux distro Galeb[1]. > > [1]: https://strahinja.srht.site/galeb/ > > this was the kind of answer I had in mind: distros, projects, > explainations on why people chose sbase instead

Re: [dev] [slock] Compile-Time Pluggable Authentication Code (passwd, pam, etc.)

2024-09-21 Thread Laslo Hunhold
On Fri, 20 Sep 2024 22:01:18 +0200 "Sebastian J. Bronner" wrote: Dear Sebastian, thanks for your hard work, interesting! > I am offering this code back to suckless to incorporate as desired and > to get feedback. If the general idea is something that is of interest > to the project, I am quite

Re: [dev] getting rid of cmake builds

2023-09-22 Thread Laslo Hunhold
On Fri, 22 Sep 2023 17:08:15 +0200 Mattias Andrée wrote: Dear Mattias, > You can used make to run ./configure automatically, all you need to > do is simply rename Makefile to makefile.in, let ./configure run `ln > -s makefile.in makefile` and create a new file named Makefile > containing: > >

Re: [dev] Am I doing this right?

2023-07-01 Thread Laslo Hunhold
On Sat, 1 Jul 2023 18:15:17 +0300 Nikita Krasnov wrote: Dear Nikita, > Is this message – an equivalent of a new forum topic or thread? Does > anyone even see this? Sorry, first time having conversations this > way. yes, welcome to this mailing list! > Also, is hard-wrapping lines at 80 charact

Re: [dev] Servers with TLS support

2023-05-07 Thread Laslo Hunhold
On Sun, 7 May 2023 22:09:23 +0200 (CEST) Sagar Acharya wrote: Dear Sagar, > I checked out the recommended webservers under rocks subpage but all > of them lack TLS support. Merecat does have it's support but it needs > systemd which my host system does not have. mini_httpd doesn't > compile. Are

Re: [dev] [license] gpl issues

2023-05-06 Thread Laslo Hunhold
On Sat, 6 May 2023 10:56:23 +0200 Страхиња Радић wrote: > [1]: https://www.gnu.org/licenses/license-list.html > [2]: https://www.gnu.org/philosophy/philosophy.html > [3]: https://www.gnu.org/licenses/why-not-lgpl.html > [4]: https://www.gnu.org/licenses/rms-why-gplv3.html Thank you for your very

Re: [dev] Using ii to connect to libera

2023-04-20 Thread Laslo Hunhold
On Thu, 20 Apr 2023 10:41:59 +0200 (CEST) Sagar Acharya wrote: Dear Sagar, > Can you please help me with a script to use ii to connect to libera? > I have tried a lot but I'm unable to make progress. if you have any hope of getting help with this, you should provide more information. What exact

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread Laslo Hunhold
On Sun, 26 Feb 2023 14:02:48 +0100 Thomas Oltmann wrote: Dear Thomas, > Looks to me like your version of quark is actually a lot newer than > 2020; Old versions of quark did not print that "dropped" message. > > Probably only tangentially related, > but I reported a bug in the connection droppi

Re: [dev] bump copyright years?

2023-02-08 Thread Laslo Hunhold
On Wed, 8 Feb 2023 21:23:45 + Al wrote: Dear Al, > Then again, I believe all suckless development is entirely done with > Git these days. So surely the datetime information recorded in each > commit makes the question moot? > > If for no other reason, I would vote for dropping the year sim

Re: [dev] [dwm] [st] benefits (or not) of -march=x86-64-v3 and gcc optimizations

2023-02-07 Thread Laslo Hunhold
On Tue, 7 Feb 2023 10:30:24 +0200 Κρακ Άουτ wrote: Dear Κρακ, > I have compiled dwm & st using -march=x86-64-v3 (tried > -march=x86-64-v2 also). To be honest they are both (dwm & st) fast > and snappy with their default configuration and I cannot spot any > difference when compiled with -march=x

Re: [dev] [st] terminfo entries won't get deleted

2023-02-03 Thread Laslo Hunhold
On Thu, 02 Feb 2023 22:33:55 + danin-sac wrote: > after looking in the Makefile I saw that the terminfo entries > wouldn't get deleted if you uninstall the program. Is there a > specific reason for that? John 13:7[0] [0]:https://www.biblegateway.com/passage/?search=John%2013%3A7&version=KJV

Re: [dev] [sbase] should tar preserve hard links info

2023-01-31 Thread Laslo Hunhold
On Tue, 31 Jan 2023 14:05:05 +0100 (CET) Andrea Calligaris wrote: Dear Andrea, > Do you think it should? > > I'm not interested in a short-term implementation, I'm more > interested if you think that it should, or if you have an opinion > against it. Im my opinion it should, because someone may

Re: [dev] Commandline Email Advice Request

2022-11-25 Thread Laslo Hunhold
On Thu, 24 Nov 2022 12:42:08 -0700 Michael Partridge wrote: Dear Michael, > Happy Thanksgiving! thanks, to you as well! > I'm having trouble using `git --send-email` to send a patch in. > > I am trying to use this email address (mcp...@nau.edu) with the > following settings in my global confi

Re: [dev] Some questions on communication suckless style

2022-10-21 Thread Laslo Hunhold
On Fri, 21 Oct 2022 12:58:47 -0500 fernandoreyesavila3 wrote: Dear Fernando, > Could you please give me some more details on bringing the ratox > project to the new api. I would be happy to contribute however I have > little programming knowledge. I think that this constitutes a pretty advanced

Re: [dev] Some questions on communication suckless style

2022-10-18 Thread Laslo Hunhold
On Wed, 19 Oct 2022 00:49:57 + Rodrigo Martins wrote: Dear Rodrigo, > toxic is a curses command line interface for the tox protocol. With > it you can do group audio calls and one on one video calls. toxic > doesn't (yet?) let you share your screen, but other tox clients, like > qtox, do. >

Re: [dev] macOS tester needed for libgrapheme

2022-10-12 Thread Laslo Hunhold
On Wed, 12 Oct 2022 10:52:48 + sek...@posteo.se wrote: Dear Sekret, > Works as expected. I've attached the config.mk how it looks after > running ./configure. perfect, thank you very much! > Have you sorted out the problem that showed up on my Macbook Air M1? The issue you mentioned is act

Re: [dev] [libgrapheme] version 2.0.0 release

2022-10-11 Thread Laslo Hunhold
On Thu, 06 Oct 2022 21:46:16 + "Hadrien Lacour" wrote: Dear Hadrien, > Hurray, I'll probably try it soon, as I was waiting for case > conversion to happen. I'm glad to hear that! Yes, it was also one of my biggest goals. > Too bad I still need to roll my theoretically incorrect but de fact

Re: [dev] macOS tester needed for libgrapheme

2022-10-11 Thread Laslo Hunhold
On Sun, 9 Oct 2022 13:42:19 + sek...@posteo.se wrote: Dear Sekret, > I've run it on a MacBook Air (M1, 2022) with an Apple M1 chip. > > % ls /usr/local/lib/libgrapheme* > /usr/local/lib/libgrapheme.2.dylib /usr/local/lib/libgrapheme.a > > The build process is attached and also contains thi

Re: [dev] macOS tester needed for libgrapheme

2022-10-09 Thread Laslo Hunhold
On Sun, 9 Oct 2022 11:24:43 +0300 Anton Konyahin wrote: Dear Anton, > I have macOS 12.6 (Monterey) on MacBook. All unit test passed, > instalation succesful. I have only warning about -s option: > > ld: warning: option -s is obsolete and being ignored > > Example from site compiled and ru

Re: [dev] macOS tester needed for libgrapheme

2022-10-09 Thread Laslo Hunhold
On Sun, 9 Oct 2022 09:57:49 +0200 simon wrote: Dear Simon, > Following the instructions worked for me on macOS 12.6. > > ls /usr/local/lib/libgrapheme* gives the following: > /usr/local/lib/libgrapheme.2.dylib /usr/local/lib/libgrapheme.a > > The example compiled successfully and the output is

[dev] macOS tester needed for libgrapheme

2022-10-08 Thread Laslo Hunhold
Hello fellow hackers, does anyone have access to a machine running the latest macOS to test if the library installation for libgrapheme works properly? It wouldn't take much time and amount to the following steps: 1. Clone libgrapheme via git clone https://git.suckless.org

[dev] [libgrapheme] version 2.0.0 release

2022-10-06 Thread Laslo Hunhold
view. Every function-manual comes with an example and the usage should be more or less obvious. With best regards Laslo Hunhold [0]: https://libs.suckless.org/libgrapheme [1]: https://dl.suckless.org/libgrapheme/libgrapheme-2.0.0.tar.gz [2]: https://semver.org/

Re: [dev] [libgrapheme] Some questions about libgrapheme

2022-09-02 Thread Laslo Hunhold
On Thu, 01 Sep 2022 21:43:06 -0300 atrtar...@cock.li wrote: Dear atrtarget, thanks for reaching out! > libgrapheme looks really useful, but I still don't get some things > from it. For example, if I need to get back one grapheme, how should > I do it since there's no `grapheme_prev_character_bre

Re: [dev] [tabbed] utf8 characters not displayed in tabs

2022-08-30 Thread Laslo Hunhold
On Tue, 30 Aug 2022 22:23:44 +0600 NRK wrote: Dear NRK, > The "proper" way (IMO) would be to build up a list of fonts which > would be capable of representing as many code-points available in the > system *right at startup* - instead of checking each unknown > code-point as we go. > > This way

Re: [dev] Replace ranlib(1) calls?

2022-08-03 Thread Laslo Hunhold
On Wed, 3 Aug 2022 16:38:14 +0200 Markus Wichmann wrote: Dear Markus, thanks for sharing your thoughts! > That design would afford some flexibility to the whole business: ar > doesn't need to know the object file format and ranlib doesn't need to > know the ar file format. I have one question

Re: [dev] Replace ranlib(1) calls?

2022-08-03 Thread Laslo Hunhold
On Mon, 1 Aug 2022 11:32:20 +0200 "Roberto E. Vargas Caballero" wrote: Dear Roberto, > There is a big important reason why scc ar does not generates a link > table, because then ar can handle any type of files, because ar is > just an archiver. Making ar(1) to generate symbol tables means that >

Re: [dev] Replace ranlib(1) calls?

2022-08-03 Thread Laslo Hunhold
On Mon, 1 Aug 2022 11:21:19 +0200 "Roberto E. Vargas Caballero" wrote: Dear Roberto, > -std=c99 is not part of any standard and our Makefiles are full of > them. as(1), ld(1), and cc(1) are not part of POSIX and we keep using > them. Again, Please stop doing this kind of patches and center in >

Re: [dev] zuccless.org

2022-07-31 Thread Laslo Hunhold
On Sun, 31 Jul 2022 01:45:39 +0200 Christoph Lohmann <2...@r-36.net> wrote: Dear Christoph, > currently we are at brcon2022 in Belgrade, smoking meats and having > fun. We decided to make it real: > > http://www.zuccless.org > > Come and join the future of meat! nice one! The link only w

Re: [dev] Replace ranlib(1) calls?

2022-07-30 Thread Laslo Hunhold
On Wed, 20 Jul 2022 12:23:01 + Tom Schwindl wrote: Dear Tom, > I've noticed that we use the non-standard ranlib(1) program to create > symbol tables for archives created by ar(1). This affects, as far as > I can tell, every creation of static libraries we have. > > ranlib(1) is, in fact, le

Re: [dev] Replace ranlib(1) calls?

2022-07-30 Thread Laslo Hunhold
On Sat, 23 Jul 2022 23:06:49 + Tom Schwindl wrote: Dear Tom, > If a system says it's POSIX compliant, we can assume that the `-s' > option exists, but there is no standard which tells us whether > ranlib(1) is available or not. while I agree with your point in general, keep in mind that the

Re: [dev] Replace ranlib(1) calls?

2022-07-30 Thread Laslo Hunhold
On Wed, 20 Jul 2022 12:23:01 + Tom Schwindl wrote: Dear Tom, > I've noticed that we use the non-standard ranlib(1) program to create > symbol tables for archives created by ar(1). This affects, as far as > I can tell, every creation of static libraries we have. > > ranlib(1) is, in fact, le

Re: [dev] Replace ranlib(1) calls?

2022-07-30 Thread Laslo Hunhold
On Sat, 23 Jul 2022 23:06:49 + Tom Schwindl wrote: Dear Tom, > If a system says it's POSIX compliant, we can assume that the `-s' > option exists, but there is no standard which tells us whether > ranlib(1) is available or not. while I agree with your point in general, keep in mind that the

Re: [dev] Suckless CMatrix clone

2022-06-16 Thread Laslo Hunhold
On Tue, 31 May 2022 08:35:11 -0400 LM wrote: Dear LM, > On Mon, May 30, 2022 at 11:33 AM Laslo Hunhold wrote: > > What functions do you need in the context of Tuxmath? > > From what I remember, it just needs to figure out where to do a clean > break for text wrapping with

Re: [dev] Suckless CMatrix clone

2022-05-30 Thread Laslo Hunhold
On Mon, 30 May 2022 07:33:24 -0400 LM wrote: Dear LM, > Thanks for the reviews. That's really helpful to know. As mentioned, > I haven't tried them myself. you're welcome! > That looks really useful. I noticed the break testing in libgrapheme. > Is it possible to use this as a replacement f

Re: [dev] Suckless CMatrix clone

2022-05-30 Thread Laslo Hunhold
On Sun, 29 May 2022 13:48:49 -0400 LM wrote: Dear LM, > I like that point. Not a fan of glib and I try to avoid software > that uses it. > > Don't know how good they are, but I've run across several lighter > utf-8 C libraries: > https://github.com/cls/libutf > https://github.com/JuliaStrings/

Re: [dev] Regarding dwm and st logo being removed

2022-04-28 Thread Laslo Hunhold
On Thu, 28 Apr 2022 18:14:14 +0200 Hiltjo Posthuma wrote: Dear Hiltjo, > Sure I don't mind you added them back. > With the inverted colors they are visible here. alright, cool. :) Thanks also for adding the dark theme. With best regards Laslo

Re: [dev] Regarding dwm and st logo being removed

2022-04-28 Thread Laslo Hunhold
On Thu, 28 Apr 2022 09:38:09 +0200 Страхиња Радић wrote: Dear Страхиња, > This can be remedied with CSS which applies white background to logos > (perhaps with some padding: to also give a bit of a > border). > > In my opinion, dark mode is unnecessary and favored by mainstream > "webdevs". I

Re: [dev] Regarding dwm and st logo being removed

2022-04-28 Thread Laslo Hunhold
On Thu, 28 Apr 2022 13:53:54 +0600 NRK wrote: Dear NRK, > Ah, that makes sense. But wouldn't it make sense to remove the logos > from *all* are projects then? > > Also since the logos are just svgs, I *think* it should be possible to > override the color of the "fill" dynmaically via css (?) If

Re: [dev] Regarding dwm and st logo being removed

2022-04-28 Thread Laslo Hunhold
On Thu, 28 Apr 2022 08:34:36 +0600 NRK wrote: Dear NRK, > Recently noticed that the dwm and st logo was removed from their > homepages[0][1]. > > I was wondering if there's any specific reason for that, or if there's > plan for a new logo(s)? > > I atleast really liked the current logos, as th

Re: [dev] Some direction with my project

2022-04-15 Thread Laslo Hunhold
NG (you already have LICENSE), ChangeLog (put this stuff in README), Makefile.am, Makefile.in, NEWS (no one cares), README.md (I'd just use README and use markdown in there), compile, config.h.in, configure, configure.ac, depcomp, install-sh, missing (for obvious reasons. Your tool can be compiled with a 5-line-Makefile. If you don't know how, let me know and I'll help you out). With best regards Laslo Hunhold

Re: [dev] sfeed: RSS/Atom parser and reader

2022-02-16 Thread Laslo Hunhold
On Fri, 11 Feb 2022 14:54:24 +0100 Hiltjo Posthuma wrote: Dear Hiltjo, > I would like to share my project I've been using and tweaking over > the years: > > sfeed is a RSS and Atom parser (and it has some format programs). nice to see it having become so advanced over the years. I remember whe

Re: [dev] [quark] Integrating form handlers with quark

2022-02-09 Thread Laslo Hunhold
On Wed, 9 Feb 2022 02:28:27 -0800 climbTheStairs wrote: Dear climbTheStairs, > I have used quark to host my static website for the past few months, > and I've been amazed by how well it works. > I want to try out the idea of keeping data processing > and data presentation separate, described on

Re: [dev] [quark] Integrating form handlers with quark

2022-02-09 Thread Laslo Hunhold
On Wed, 9 Feb 2022 11:37:37 +0100 Teodoro Santoni wrote: Dear Teodoro, > A reverse proxy is vital only if your server can serve only HTTP(S) > and little else. Otherwise it just prevents urls from looking ugly: > you can serve your other process for input process on another port and > put http:/

Re: [dev] libgrapheme versioning

2022-01-28 Thread Laslo Hunhold
On Wed, 26 Jan 2022 22:08:43 -0300 "Pedro Lucas Porcellis" wrote: Dear Pedro, > While packaging libgrapheme for Alpine, it was pointed out that the > generated .so file isn't versioned, which apparently it is not bad, > but it was questioned why. I don't know if it's a slip or if it's a > delibe

Re: [dev] [slock] Doesn't work when password contains non-ASCII characters

2022-01-09 Thread Laslo Hunhold
On Sun, 9 Jan 2022 09:45:49 +0100 meator wrote: Dear meator, > Slock doesn't work when the user's password contains non-ASCII > characters. I have discussed this in the IRC channel, because I had > problems with 'ů'. > > Please fix this or document the fact that slock doesn't support > non-ASCI

Re: [dev] Special target ".POSIX" in Makefiles

2022-01-01 Thread Laslo Hunhold
On Sat, 1 Jan 2022 23:30:39 +0100 Ralph Eastwood wrote: Dear Ralph, > Those are both useful suggestions! Thank you! you're very welcome! :) With best regards Laslo

Re: [dev] Special target ".POSIX" in Makefiles

2022-01-01 Thread Laslo Hunhold
On Sat, 1 Jan 2022 17:03:41 +0100 Ralph Eastwood wrote: Dear Ralph, > Thanks for pointing out that technique, I've utilised it in the past > and it's a shame that it's not more well-known... I've seen many a > GNUism in its place... yeah, it makes a lot of sense and is nice and simple. > The i

Re: [dev] Special target ".POSIX" in Makefiles

2022-01-01 Thread Laslo Hunhold
On Sat, 1 Jan 2022 14:08:24 +0100 Ralph Eastwood wrote: Dear Ralph, > So... makellint? :D > I like it; it seems 'makel' is unused as a project name. and even if, it's not like names are reserved. When some 13-year-old kid dumps some Rust-crap with a name on GitHub I wouldn't see it as reserved.

Re: [dev] Special target ".POSIX" in Makefiles

2022-01-01 Thread Laslo Hunhold
On Sat, 1 Jan 2022 13:22:48 +0100 Mattias Andrée wrote: Dear Mattias, > libzahl is my only project with a German name, and it's was called > libzahl because the bold Z used represent the integers stands for > Zahl, but I do have projects with names in different languages (I > also have libskrift

Re: [dev] Special target ".POSIX" in Makefiles

2022-01-01 Thread Laslo Hunhold
On Sat, 1 Jan 2022 10:33:22 +0100 Mattias Andrée wrote: Dear Mattias, first off, happy new year to all of you! > Thanks for pointing that it, I didn't find it in my search. > I renamed it to mklint. This is also confusing as mk(1) by plan9 exists, but you explicitly target POSIX make(1). make

Re: [dev] Special target ".POSIX" in Makefiles

2021-12-31 Thread Laslo Hunhold
On Fri, 31 Dec 2021 11:16:18 +0100 Hiltjo Posthuma wrote: Dear Hiltjo, > In my opinion a practical way is to really test it on different > systems (bleeding edge Linux, older Debian stable, NetBSD, OpenBSD) > and GNU/Make, different BSD make programs. > > This doesn't cover the POSIX compatibil

Re: [dev] Special target ".POSIX" in Makefiles

2021-12-31 Thread Laslo Hunhold
On Fri, 31 Dec 2021 01:52:42 -0800 Arthur Williams wrote: Dear Arthur, > I too fell victim to the GNU trap and thought "?=" was standard and > actually useful. hehe this thread here feels like a self-help-thread of the newly POSIX-make-awakened! > Completely forgot about the -e flag. Now I nee

Re: [dev] Special target ".POSIX" in Makefiles

2021-12-31 Thread Laslo Hunhold
On Fri, 31 Dec 2021 12:49:46 +0600 NRK wrote: Dear NRK, > Hmm, I was under the impression that `?=` was accepted into POSIX. > But I cannot find any mention of it in the posix manpage (man 1p > make) so I guess I was wrong. > > What would be a posix replacement for `?=` ? I assume something lik

Re: [dev] Special target ".POSIX" in Makefiles

2021-12-30 Thread Laslo Hunhold
On Thu, 30 Dec 2021 21:17:32 +0100 Mattias Andrée wrote: Dear Mattias, > I've actually being thinking of writing a makefile linter. > How interested would people be in such a tool? very interested! Even though, when you implement the logic, you might as well go all the way and offer a make(1) t

Re: [dev] Special target ".POSIX" in Makefiles

2021-12-30 Thread Laslo Hunhold
On Thu, 30 Dec 2021 17:49:23 +0100 crae...@gmail.com wrote: Dear craekz, > As far as I can see, we could add `.POSIX` to the following programs: > dwm, dmenu, dwmstatus, sent and tabbed > I've just looked over the Makefiles very briefly, so I may have > overseen something. Note: I just picked out

[dev] [libgrapheme] version 1 release

2021-12-22 Thread Laslo Hunhold
and the usage should be more or less obvious. With best regards Laslo Hunhold [0]: https://libs.suckless.org/libgrapheme [1]: https://dl.suckless.org/libgrapheme/libgrapheme-1.tar.gz

Re: [dev] [dwm] dwm breaks on synchronized screens

2021-11-12 Thread Laslo Hunhold
On Thu, 11 Nov 2021 19:34:08 +0100 Thomas Oltmann wrote: Dear Thomas, > What do I do about this? > Is it even a bug or just me using dwm for stuff it's not intended to > do? One way or another, how can I do my presentations without > fighting the WM all the time? do you have a way so we can rep

Re: [dev] Whether a css selector applies to given html surf code

2021-11-10 Thread Laslo Hunhold
On Tue, 26 Oct 2021 20:44:52 +0200 Страхиња Радић wrote: Dear Страхиња, > If anyone wants to use other software, by all means they should. > There's nothing wrong with that, but on the other side, that > shouldn't influence suckless programs. I completely agree with that. Popularity should neve

Re: [dev] Wayland compositors

2021-09-15 Thread Laslo Hunhold
On Tue, 14 Sep 2021 15:21:58 +0600 NRK wrote: Dear NRK, > Adding to what Laslo has already said: > > I think it's laughable that that wayland devolopers claim wayland to > be a replacement for X while actively ignoring many use-case and > forcing their "perfect frame" philosophy onto the users.

Re: [dev] Wayland compositors

2021-09-09 Thread Laslo Hunhold
On Wed, 8 Sep 2021 20:34:20 + Hadrien Lacour wrote: Dear Hadrien, > This, it would have been a great goal to modularize X11 and keep the > worthy parts, not just reduce it to an exercise in "minimalism" (and > complete lack of portability) and expect the free FOSS market to > magically solv

Re: [dev] Wayland compositors

2021-09-08 Thread Laslo Hunhold
On Tue, 31 Aug 2021 14:28:29 +0100 Nick wrote: Dear Nick, > Any thoughts, experiences, recommendations? the discussion has been very fruitful. Let me share my thoughts. Wayland the protocol is actually rather simple. It's a very thin messaging layer between a compositor and clients, nothing mo

Re: [dev] Auditing requiirement for sbase

2021-07-29 Thread Laslo Hunhold
On Thu, 29 Jul 2021 15:00:17 -0300 EuAndreh wrote: Dear EuAndreh, > The README of the sbase project [0] classifies tools has being > audited or not. Looking at the log of the repository I could only > find soft references to what such audit entails, such as [1] and [2]. > > From what I could un

Re: [dev] sshd?

2021-07-27 Thread Laslo Hunhold
On Wed, 28 Jul 2021 03:05:43 +0300 anigger@national.shitposting.agency wrote: > MOSH Thanks for the recommendation; I didn't know about that one[0]! It's just a little worrying that there seems to be little activity in the codebase, that might also just as well indicate a mature project. With be

Re: [dev] Better naming for arg.h API

2021-07-18 Thread Laslo Hunhold
On Thu, 8 Jul 2021 21:06:37 +0200 Hiltjo Posthuma wrote: Dear Hiltjo, > Can you please stop spamming the mailinglist? I already explained the > reasons why arg.h won't be changed. > > Feel free to blame me for being rude or whatever. I agree here. Certainly arg.h is not a big "construction sit

Re: [dev] Enhanced arg.h from quark

2021-07-06 Thread Laslo Hunhold
On Tue, 06 Jul 2021 00:08:04 + Sebastian LaVine wrote: Dear Sebastian, > Might I recommend using https://0x0.st or > https://ix.io for pastebins. You can read and > write to them using curl, or still use the browser > but without the extra fat and JS of pastebin.com. I'd recommend just atta

Re: [dev] Update outdated suckless website

2021-06-11 Thread Laslo Hunhold
On Fri, 11 Jun 2021 11:38:20 +0200 Hiltjo Posthuma wrote: Dear Hiltjo, Dear Martin, > Thank you for the valuable feedback. I also want to thank you, Martin, for your feedback! I've assigned Scrum-ID #S1H3I3T7 to this ticket. > 200ms seems still a bit high, maybe we could use geolocated CDNs of

Re: [dev] Sxmo presentation at AlpineConf (Sat May 15, 14:30 UTC)

2021-05-14 Thread Laslo Hunhold
On Fri, 14 May 2021 15:59:47 +0200 Maarten van Gompel wrote: Dear Maarten, > I just wanted to drop a little announcement that this weekend on > AlpineConf 2021, we will present Sxmo, the simple X mobile > environment. As it is largely based on the suckless stack of tools > (dwm, dmenu, svkbd, st

Re: [dev] Ada not Rust

2021-05-13 Thread Laslo Hunhold
On Thu, 13 May 2021 05:54:03 +0300 Greg Minshall wrote: Dear Greg, > > I'm just glad that I, as a numerical mathematician, don't have to > > use MATLAB anymore. I initiated and finalized that the current > > lecture on numerical mathematics here in Cologne, which I > > co-supervise, is using Jul

Re: [dev] Ada not Rust

2021-05-11 Thread Laslo Hunhold
On Tue, 11 May 2021 11:15:37 +0300 Greg Minshall wrote: Dear Greg, > i'm ignorant, but curious. a friend who does high performance > computing is a fan of Julia, and in the past pointed me at > > https://www.nextplatform.com/2017/11/28/julia-language-delivers-petascale-hpc-performance/ > > i'

Re: [dev] Ada not Rust

2021-05-04 Thread Laslo Hunhold
On Sun, 02 May 2021 18:17:45 -0400 "Greg Reagle" wrote: Dear Greg, > Do you have any other suggestions for alternatives to C? this question is too general. For academic purposes (HPC, data analysis, numerical mathematics, statistics, etc.) I can recommend Julia. > I haven't started re-writing

Re: [dev] Ada not Rust

2021-05-02 Thread Laslo Hunhold
On Wed, 21 Apr 2021 02:38:48 +1200 Miles Rout wrote: Dear Miles, > On Tue, Apr 20, 2021 at 06:45:40AM -0700, Jeremy wrote: > > Regarding readability: in terms of the just the standard libraries, > > I agree that Rust is more readable than C, especially it comes to > > iterating and generics. >

Re: [dev] Ada not Rust

2021-05-02 Thread Laslo Hunhold
On Tue, 20 Apr 2021 06:29:30 -0400 "Greg Reagle" wrote: Dear Greg, > Thank you for your explanation Laslo Hunhold. I wholeheartedly agree > with you about the fallibility of human programmers, and the > vulnerability of C to errors. Even though I am a fan of the suckless &

Re: [dev] Ada not Rust

2021-04-20 Thread Laslo Hunhold
On Mon, 19 Apr 2021 16:19:18 -0400 "Greg Reagle" wrote: Dear Greg, let me give a short overview of Ada and why I think it's great: Ada is all about dependability (that's why it was developed and is still widely used in a wide range of fields) and many things you'd find in other languages are not

Re: [dev] Checksums and Sig files for release gzip

2021-04-17 Thread Laslo Hunhold
On Sat, 17 Apr 2021 17:42:50 +0200 Mattias Andrée wrote: Dear Mattias, > I've completely ignored Rust. What's the problem with it? in regard to my argument: It has abysmal compile times and the compiler is extremely bloated. In general though, I see multiple issues with it: The crate-system co

Re: [dev] Checksums and Sig files for release gzip

2021-04-17 Thread Laslo Hunhold
On Wed, 14 Apr 2021 09:05:01 +0300 Sergey Matveev wrote: Dear Sergey, > If we a talking here about checking software integrity, then speed is > important. Millions of people check the hash of downloaded files -- if > it is slow, then huge quantity of time/energy is wasted. Less time you > spent

Re: [dev] Checksums and Sig files for release gzip

2021-04-17 Thread Laslo Hunhold
On Sat, 17 Apr 2021 07:45:16 +0200 (CEST) Sagar Acharya wrote: Dear Sagar, > Ok. But this is a behavioral change right? How can a patch help in > this case? > > Admins always protest the decision in almost every community if it > isn't theirs. Am I suggesting something harmful here? It takes a

Re: [dev] Completeness suckless

2021-04-09 Thread Laslo Hunhold
On Fri, 9 Apr 2021 14:54:31 +0200 (CEST) Sagar Acharya wrote: Dear Sagar, > I recently wrote this article > > https://designman.org/sagaracharya/blog/trusting_no_one > > being absolutely unaware about suckless and this was brought to my > attention. interesting article! > Suckless's philoso

Re: [dev] st: enlarge font

2021-03-22 Thread Laslo Hunhold
On Mon, 22 Mar 2021 16:03:39 + Wesley Pannell wrote: > Can we remove this email address from the list? This is rediculous. Welcome to the internet.

Followup: Re: [dev] [quark] Shouldn't it redirect site.com/ to /index.html?

2021-01-24 Thread Laslo Hunhold
On Fri, 22 Jan 2021 11:16:13 -0800 Spenser Truex wrote: > If you navigate to my site: > http://equwal.com > It doesn't redirct to index.html, since I don't have a program > performing redirects on there like varnishd. > > Previously I was using varnishd in front of quark to do this, and I > had

Re: [dev] [quark] Shouldn't it redirect site.com/ to /index.html?

2021-01-24 Thread Laslo Hunhold
On Fri, 22 Jan 2021 11:16:13 -0800 Spenser Truex wrote: Dear Spenser, > If you navigate to my site: > http://equwal.com > It doesn't redirct to index.html, since I don't have a program > performing redirects on there like varnishd. > > Previously I was using varnishd in front of quark to do thi

Re: [dev] [st] When shrinking the width of a st window, overflowing text gets cut out and it is no longer retrievable, not even if the width is reset to the original one

2021-01-06 Thread Laslo Hunhold
On Tue, 05 Jan 2021 20:16:57 +0100 LuxGiammi wrote: Dear Luxgiammi, > It's my first message in this mailing list. > I've been using st for more than one year and I've always had the > intention to ask this. I know that there must be a way to solve the > problem (in fact, I started to study X p

Re: [dev] [st] Undeleted parts of characters

2021-01-01 Thread Laslo Hunhold
On Thu, 31 Dec 2020 15:43:59 +0100 Filip wrote: Dear Filip, > I do not know why but for some reason very long characters like "|" > "/" "\" "å" etc does not get fully deleted in terminal. Instead they > leave annoying dots at the top; the absolute top of the characters > remain. This is annoying

Re: [dev] [slstatus] Inactivity and continuation of development

2020-11-30 Thread Laslo Hunhold
On Mon, 30 Nov 2020 17:13:32 +0100 Aaron Marcher wrote: Dear Aaron, > I have been very inactive here for the last year because of work and > personal reasons. However, I am alive! :-) > > Regarding my slstatus maintainership: In the next weeks I will dig > through all the discussion on the ma

Re: [dev] [sbase][tar] GNU tar support

2020-11-25 Thread Laslo Hunhold
On Wed, 25 Nov 2020 22:49:32 +0100 Mattias Andrée wrote: Dear Mattias, > Concerning farbfeld, it is quite a different thing to create a new > simpler standard than supporting an already existing but complex > standard. Farbfeld was a good first step in moving towards simpler > image formats, alt

Re: [dev] [sbase][tar] GNU tar support

2020-11-25 Thread Laslo Hunhold
On Wed, 25 Nov 2020 18:32:36 +0100 Thomas Oltmann wrote: Dear Thomas, > > if gnu tar proprietary? > > No. I think Laslo meant 'proprietary' as in 'ad hoc' or 'incompatible' > (with standard implementations). yeah, I used a pretty "drastic" word to describe it. All will agree that GNU-tar is

Re: [dev] [sbase][tar] GNU tar support

2020-11-25 Thread Laslo Hunhold
On Wed, 25 Nov 2020 07:51:22 -0500 Cág wrote: Dear Cág, > A quick question: for "POSIX tar archive (GNU)" files tar prints > tar: unsupported tar-filetype L > > Is GNU tar support out of scope? there's probably no way to implement those GNU-extensions in a good and suckless way. The FSF has th

Re: [dev] On how dwm hides windows

2020-06-24 Thread Laslo Hunhold
On Wed, 24 Jun 2020 14:39:03 +0200 "Silvan Jegen" wrote: Dear Silvan, > The first beginnings are here (not by me): > > https://github.com/djpohly/dwl > > It uses the wlroots[0] wayland compositor library which a lot of > people may not consider suckless however. I think the decision to use > t

Re: [dev] Re: [slstatus] temperature module acts wierd on OpenBSD

2020-06-16 Thread Laslo Hunhold
On Tue, 16 Jun 2020 20:53:34 +0200 Mattias Andrée wrote: Dear Mattias, > I'm assuming temp.value i an `int`, as %d is used. The problem was > probably that `1E6` is actually a `double` rather than an `int`, > as the whole expression is promoted to `double`, because `bprintf` is > (I assume) vari

Re: [dev] Re: [slstatus] temperature module acts wierd on OpenBSD

2020-06-16 Thread Laslo Hunhold
y that; thanks for sending in this patch! What is the origin of this problem? Does this have something to do with guaranteed constant-sizes in Posix? With best regards Laslo Hunhold

Re: [dev] [ANNOUNCE] vis-0.6

2020-06-07 Thread Laslo Hunhold
On Sun, 7 Jun 2020 13:16:57 +0200 Marc André Tanner wrote: Dear Marc, > I'm pleased to announce a new version of the vis editor, combining > modal editing with built-in support for multiple selections, > structural regular expressions and Lua scripting capabilities. this looks really cool! I'm

Re: [dev] Infnite loop in drawbar() when using attachbelow and sending windows between monitors

2020-06-06 Thread Laslo Hunhold
On Sat, 6 Jun 2020 13:11:02 +0200 Hiltjo Posthuma wrote: Dear Hiltjo, > I don't use this patch, but can someone push it to the wiki so anyone > can easily use the fix? I've included the change in both patch-versions, tested it against 6.2 and pushed it into the wiki. With best regards Laslo

[dev] [slcon7] Cancellation of the suckless conference 2020

2020-05-27 Thread Laslo Hunhold
ncial hardships many of us are enduring due to the developing depression. We hope to be able to host a conference next year and welcome you there. Thank you for your support; we wish you all the best for what is ahead! With best regards Laslo Hunhold

Re: [dev] [smu] Updated smu ready for suckless.org?

2020-04-30 Thread Laslo Hunhold
On Thu, 30 Apr 2020 07:57:01 +0200 Karl Bartel wrote: Dear Karl, > I tried to get the task "Improve the Markdown parser used by the > suckless wiki called 'smu' to conform more to Markdown" from > https://suckless.org/project_ideas/ done. You can find a summary of > the differences introduced by

Re: [dev] Scrollback utility for use with st

2020-04-06 Thread Laslo Hunhold
On Mon, 06 Apr 2020 09:58:06 -0400 "Greg Reagle" wrote: Dear Greg, > Yes that happen to me occasionally, which is why I use the scrollback > patch for st. I find it much easier to hit Shift+PageUp than to > rerun a command. And when the output of a command changes with time, > re-running it mi

Re: [dev] Scrollback utility for use with st

2020-04-06 Thread Laslo Hunhold
On Mon, 6 Apr 2020 13:27:21 +0200 Laslo Hunhold wrote: > I'm definitely not an expert in terminal emulators (Roberto, Hiltjo > and Christoph are), but the case is pretty clear to me when I look at > scroll[0], which Jan and Jochen are working on right now. > If you look at scro

Re: [dev] Scrollback utility for use with st

2020-04-06 Thread Laslo Hunhold
On Mon, 6 Apr 2020 11:43:29 +0200 Hadrien Lacour wrote: Dear Hadrien, > If what you said is true about having to reimplement a terminal > emulator in the scrollback utility, it completely makes sense to > integrate it. I'm definitely not an expert in terminal emulators (Roberto, Hiltjo and Chri

Re: [dev] Scrollback utility for use with st

2020-04-06 Thread Laslo Hunhold
On Mon, 06 Apr 2020 08:48:38 +0200 "Silvan Jegen" wrote: Dear Silvan, > I honestly never use tmux either. If I think I may need the output of > a program, I just redirect it to a file/editor/pager. yeah, same here. But how often do you get some output and think "oh, I actually needed that" and

Re: [dev] Scrollback utility for use with st

2020-04-05 Thread Laslo Hunhold
On Sun, 05 Apr 2020 16:52:15 +0200 "Silvan Jegen" wrote: Dear Silvan, > Yes, the scrollback buffer can be implemented by a different tool like > tmux for example. That's why this functionality is not implemented in > st from what I understand. Separation of concerns and so on. > > I can see why

Re: [dev] Scrollback utility for use with st

2020-04-05 Thread Laslo Hunhold
On Sun, 5 Apr 2020 12:11:09 +0200 Georg Lehner wrote: Dear Georg, > A question: why is the scrollback-patch not included in `st` already exactly my point. I see no reason why there can't at least be a scrollback, which defaults to 0 in config.h. Wouldn't this make all sides happy? With best re

Re: [dev] Scrollback utility for use with st

2020-04-03 Thread Laslo Hunhold
On Thu, 2 Apr 2020 21:14:11 +0200 Georg Lehner wrote: Dear Georg, > I just figured out, that `st` already has an unlimited scrollback > buffer > - kind of. > > Run `st -o /tmp/unlimited_scrollbackbuffer`. > > Than inside the `st` terminal, you can `less`, `vi` ... whatever you > want. > > Fo

  1   2   3   >