On Sat, Feb 03, 2024 at 09:04:04PM +, NRK wrote:
> Having trouble unsubscribing? Worry not, coach NRK is at your service!
> For a fair pay of 1337 XMR, you'll receive:
>
> ★★★ A comprehensive guide on how to unsubscribe from the suckless dev mailing
> list ★★★
>
> Offer available for a limit
:)
Having trouble unsubscribing? Worry not, coach NRK is at your service!
For a fair pay of 1337 XMR, you'll receive:
★★★ A comprehensive guide on how to unsubscribe from the suckless dev mailing
list ★★★
Offer available for a limited time only.
- NRK
(replying to Laslo)
> which is basically a CGI-interface and thus not within quark's scope.
thttpd has a patch that adds basic CGI support, and I've quickly scanned the
patch, and it seems super simple.. perhaps you could use that in one way or
another.
I don't mean to say "support intellectual pr
Hey, Laslo.
Yeah, that's fine.. it's like "stable release" for normies.
Ah. I kind-of like Quark.. I don't want to go try thttpd..
It does NOT work XD
In fact - it seems to work much less.. like the opposite from before.
I get like the IP (localhost) dropped - -
usually it's IP (localhost) 200(o
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
If you guys want - perhaps we can play the printf game, or rather - the
logging game?
Ah, I see.
I forgot how to use git after such a long absence from programming.. +6
months.
I ran the command and it's up to date, last commit is
68b4f733b2755762e43df90f73db5a6ec8d14104 on both of my sites.
I see.
I can test the patch, but I don't think I'm using AF_INET6 as I disabled IPv6
in Fr
On Sun, Feb 26, 2023 at 3:53 PM wrote:
>
> I did a git clone like it says on the main Quark web-site, and doing `mandoc
> -a quark.1` it shows '2020-09-27', and that's what I am using.
> Unless that's wrong and/or there's another way to get the version number -
> I'd
> like to know.
Ah i see. Run
I did a git clone like it says on the main Quark web-site, and doing `mandoc
-a quark.1` it shows '2020-09-27', and that's what I am using.
Unless that's wrong and/or there's another way to get the version number -
I'd
like to know.
> which meant that quark would likely drop legitimate connections
> Reread Laslo's message and look at the source code as he suggested in
the mentioned message.
I cannot afford that, I have health problems :(.
Regardless - I am getting only ~5 requests per minute, and my biggest file
is <3M, so even given the attack has a super-slow Tor circuit connection
of say
Hi fossy,
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 dropping code some time ago,
which meant that quark would likely drop legitimat
On 23/02/25 12:59PM, fo...@dnmx.org wrote:
> Tried -s 128 -t 8, doesn't seem to do jack shit..
> Got less than 10 connection logs from Quark and then another dropped one..
> Is there any other reason Quark would print-out 'dropped', other than
> connection pool at max?
>
> I restarted the jail, so
Tried -s 128 -t 8, doesn't seem to do jack shit..
Got less than 10 connection logs from Quark and then another dropped one..
Is there any other reason Quark would print-out 'dropped', other than
connection pool at max?
I restarted the jail, so Quark's memory and stuff should have been reset.
Hey, I just read the quark.1 .
I see the -s and -t options lol. I shall experiment.
Hi, Laslo.
Sorry, I might not have been best at explaining problem, but then again - I
didn't quite understand problem.. but said all I did understand.
> one of my development goals for quark was to have no memory allocations at
runtime.
Right, I knew that.. but what about memory allocation BEFOR
You are a brainless joke.
On Sat, Feb 25, 2023 at 09:50:42AM -0500, fo...@dnmx.org wrote:
> Hello.
> Before I start, I want to clarify 2 things:
> 1. I'm not 100% sure if it's a Quark problem, but there are like 2/4th
> chance that it is.
> 2. I'm hosting my site over the Tor network
>
> Problem I have: software runs, can
Hello.
Before I start, I want to clarify 2 things:
1. I'm not 100% sure if it's a Quark problem, but there are like 2/4th
chance that it is.
2. I'm hosting my site over the Tor network
Problem I have: software runs, can access it from localhost via curl, but
cannot access it from Tor
What happens
On Fri, Jun 05, 2020 at 03:05:49PM -0400, Kyryl Melekhin wrote:
> This bug is very exceptional and will only affect users who run other
> terminal programs with st.
> For example running
> " st -e vim . "
> " st -e lynx "
> etc ...
>
Hi Kyryl,
Thanks for the report.
> The bug happens randomly,
This bug is very exceptional and will only affect users who run other
terminal programs with st.
For example running
" st -e vim . "
" st -e lynx "
etc ...
The bug happens randomly, and on some systems may not even exist, very
hard to reproduce and predict. On my system with clean st build
changes
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
hey
--
Joseph Graham
> dev+unsubscr...@suckless.org
Your subscription has been prolonged.
dev+unsubscr...@suckless.org
He is another one for signals populate-popup/context-menu.
I'm not sure that is really necessary, but here, it's done.
On Thu, Feb 6, 2014 at 7:15 PM, Christoph Lohmann <2...@r-36.net> wrote:
> Greetings.
>
> On Thu, 06 Feb 2014 19:15:13 +0100 Quentin Rameau wrote:
>> As the subject of the mail t
Greetings.
On Thu, 06 Feb 2014 19:15:13 +0100 Quentin Rameau wrote:
> As the subject of the mail tells, this is a simple signal handling
> adjustment for page title modification.
The patch has been applied. Thanks for sending it.
Sincerely,
Christoph Lohmann
As the subject of the mail tells, this is a simple signal handling
adjustment for page title modification.
0001-deprecating-signal-title-changed-for-notify-title.patch
Description: Binary data
You might want to try that using the right header :-)
On 13 Jun 2013 10:21, "Thuban" wrote:
>
>
signature.asc
Description: Digital signature
On Wed, Dec 26, 2012 at 7:30 AM, Johny Why wrote:
> dev+unsubscribe-dig...@suckless.org
You send a message to that address (body isn't important).
~cjh
dev+unsubscribe-dig...@suckless.org
On Mon, Aug 06, 2012 at 10:13:01AM +0200, Anselm R Garbe wrote:
> Read
>
> http://suckless.org/community
>
> to learn the unsubscription procedure.
>
Or the email headers...
Read
http://suckless.org/community
to learn the unsubscription procedure.
Welcome to the suckless mailing list!
You have been succesfully subscribed again.
Ad eternum
On Aug 6, 2012, at 8:34, David Dušanić wrote:
>
> With this patch, your Makefile works with my make (GNU Make 3.81)
Thanks for your patch. I modyfied Makefile accordingly and pushed it to github.
--
Michał Siejak
On Wed, Oct 19, 2011 at 09:37:52PM +0200, Michał Siejak wrote:
> Hello.
[...]
> Source code is here: https://github.com/Nadrin/xlsh
> Example screenshot is here: https://github.com/Nadrin/xlsh/wiki
>
> If any of you guys find it useful let me know. :) Constructive
> criticism/peer review is more t
On Sat, Aug 21, 2010 at 2:12 AM, pancake wrote:
> 80 or 78? :)
Good point. I personally use 78 because, if you follow the Python
suggestion of 79 characters and reserve 1 more character for +/-/>
indicators in diff(1) output, then your code will be readable in
terminals, editors, and also in pat
2010/8/21 Suraj Kurapati :
> I like to put documentation at the head of a file because that's only
> part anyone will read before deciding if it's worth spending their
> time to delve into the rest of the shell script. Also, I don't like
> messing up my program's indentation because I have to emit
On Sat, Aug 21, 2010 at 4:22 AM, yy wrote:
> 2010/8/19 Suraj Kurapati :
>> On Tue, Aug 17, 2010 at 7:54 PM, Suraj Kurapati wrote:
>> #!/bin/sh
>> # your program description & usage documentation here
>> # nicely formatted and beautified to fit 80 columns
>> # NOTE: the blank line below is the end
2010/8/19 Suraj Kurapati :
> On Tue, Aug 17, 2010 at 7:54 PM, Suraj Kurapati wrote:
>> On Tue, Aug 17, 2010 at 8:40 AM, Alexander Teinum wrote:
>>> What is the most concise way of outputting a usage and help text?
>>
>> For my programs, the --help option simply displays their manpage. :-)
>
> Alt
80 or 78? :)
Sent from my iPod
On Aug 21, 2010, at 2:59 AM, Noah Birnel wrote:
On Thu, Aug 19, 2010 at 11:06:40AM -0700, Suraj Kurapati wrote:
On Tue, Aug 17, 2010 at 7:54 PM, Suraj Kurapati
wrote:
Alternatively, in simple shell scripts (for which writing a manpage
would be overkill), I s
On Thu, Aug 19, 2010 at 11:06:40AM -0700, Suraj Kurapati wrote:
> On Tue, Aug 17, 2010 at 7:54 PM, Suraj Kurapati wrote:
> Alternatively, in simple shell scripts (for which writing a manpage
> would be overkill), I simply print the script file's comment header
> using sed(1):
>
> #!/bin/sh
> # yo
On Tue, Aug 17, 2010 at 7:54 PM, Suraj Kurapati wrote:
> On Tue, Aug 17, 2010 at 8:40 AM, Alexander Teinum wrote:
>> What is the most concise way of outputting a usage and help text?
>
> For my programs, the --help option simply displays their manpage. :-)
Alternatively, in simple shell scripts
On Wed, Aug 18, 2010 at 05:55:10PM +0200, Alexander Teinum wrote:
> I’d like to write a KISS option parser that accepts “program -c -a -f
> some_file”, but not “program -ca -fsome_file”. I prefer to keep the
> rules simple.
take a look at the ARGBEGIN and ARGEND macro's in Plan 9.
pgpoEUvuWrFez.p
On Wed, Aug 18, 2010 at 05:55:10PM +0200, Alexander Teinum wrote:
> Is it okay to use three dots in the usage text? (See echo’s man page.)
> I think it means that you can repeat what’s before the three dots.
It is ok and they should be used. And it should be 3 dots, not … so
usage is in ASCII. A
2010/8/18 Alexander Teinum :
> I’d like to write a KISS option parser that accepts “program -c -a -f
> some_file”, but not “program -ca -fsome_file”. I prefer to keep the
> rules simple.
Such a simple option set probably doesn't actually *need* a parser. I
don't think any lines would be freed up i
On Wed, Aug 18, 2010 at 10:27 AM, Kris Maglione wrote:
>
> GNU man has the annoying and difficult to stop habit of filling the entire
> width of the terminal rather than wrapping at 80 chars. And if you set
> $MANWIDTH or $COLUMNS to 80 and the terminal isn't that wide, you wind up
> with badly br
(Sorry for not quoting names. It’s cumbersome to do with more than one
person in Gmail.)
> With the above rules this should be: flo [-cfrtw arg] [what[,from][-to]]
I think that’s too little information.
> It also just makes the usage easier to read, in my opinion. Dropping a
> few characters jus
On 18 August 2010 15:37, Alexander Teinum wrote:
> But we don’t need the brackets. As long as the usage text is
> unambiguous, then they don’t add any information. Am I right?
Two instances which make this untrue:
> ar [-]key archive [files...]
> eg [-b from to] files...
It also just makes the
But we don’t need the brackets. As long as the usage text is
unambiguous, then they don’t add any information. Am I right?
Alexander
On Tue, Aug 17, 2010 at 08:52:37PM +0400, anonymous wrote:
> usage: cmd [-abcde] [-f file] [-g pattern] [file ...]
What about cmd [-abcde] [-fg arg] [file ...]?
> usage: flo [-c id] [-f from] [-r id] [-t to] [-w what] [what[,from][-to]]
With the above rules this should be: flo [-cfrtw arg] [what[,
On Tue, Aug 17, 2010 at 08:07:05PM +0200, Alexander Teinum wrote:
> > I think the best format for usage is something like what Plan 9
> > utilities use (BSD use the same):
> >
> > usage: cmd [-abcde] [-f file] [-g pattern] [file ...]
>
> Options without values are combined? Is that correct?
Yes.
On Tue, Aug 17, 2010 at 8:27 PM, Kris Maglione wrote:
> GNU man has the annoying and difficult to stop habit of filling the entire
> width of the terminal rather than wrapping at 80 chars. And if you set
> $MANWIDTH or $COLUMNS to 80 and the terminal isn't that wide, you wind up
> with badly broke
On Tue, Aug 17, 2010 at 07:54:44PM -0700, Suraj Kurapati wrote:
On Tue, Aug 17, 2010 at 8:40 AM, Alexander Teinum wrote:
What is the most concise way of outputting a usage and help text?
For my programs, the --help option simply displays their manpage. :-)
man(1) is better suited for informa
On Tue, Aug 17, 2010 at 8:40 AM, Alexander Teinum wrote:
> What is the most concise way of outputting a usage and help text?
For my programs, the --help option simply displays their manpage. :-)
man(1) is better suited for information display (text-wrapping to 80
characters or $COLUMNS, paginati
> I think the best format for usage is something like what Plan 9
> utilities use (BSD use the same):
>
> usage: cmd [-abcde] [-f file] [-g pattern] [file ...]
Options without values are combined? Is that correct?
> With these rules flo usage should be
>
> usage: flo [-c id] [-f from] [-r id] [-t
On Tue, Aug 17, 2010 at 05:40:40PM +0200, Alexander Teinum wrote:
> What is the most concise way of outputting a usage and help text?
>
> Must the usage text be unambiguous when it comes to valid combinations?
No, compatibility of options should be described in man page.
> What should the progra
What is the most concise way of outputting a usage and help text?
Must the usage text be unambiguous when it comes to valid combinations?
What should the program option or options be named that show the usage
or help text?
Are there any existing standards for usage and help text?
How should the
On Sat, May 15, 2010 at 12:35:41AM +0200, hiro wrote:
> That's why I always said "suckless" is stupid. People have too high
> expectations when they read it!
It's not plan9 enough!!
--
Marvin Vek
-
/*
* We used to try various strange things. Let's not.
*/
linux-2.2.16/fs/buffer.c
That's why I always said "suckless" is stupid. People have too high
expectations when they read it!
«Dawning horror tinged with self-loathing crept slowly over the face
of mobi phil as he described his "text editor" and by extension his
vision of "suckless" to others during a seemingly innocuous email
exchange.»
Uriel was *not even* involved. A weird (and incredible) day, indeed.
On Fri, May 14, 2010 at 5:55 PM, mobi phil wrote:
> By the way. Ion3 is less bloated than any of the wi, wii, wi,
> wii or drm... Isn't it a bloat or "not suckles" to have the same 3
> times?
Has anyone really been far even as decided to use even go want to do
look more like?
--
# Kurt
Well, I had a funny day here, but I think I knocked at the wrong door...
By the way. Ion3 is less bloated than any of the wi, wii, wi,
wii or drm... Isn't it a bloat or "not suckles" to have the same 3
times?
Anders Andersson said "You're insane". Two of them in the same place
is too dang
2009/11/10 Kris Maglione :
> On Mon, Nov 09, 2009 at 07:20:28PM -0600, tosh wrote:
>>
>> For fucks sake it's not that big of a deal is it? I don't read the
>> discussions, hence the unsubscribe. Gmail adds an unsubscribe link,
>> apparently it doesn't work. No need to be a dick.
>
> It really is, g
On Mon, 9 Nov 2009 19:30:54 -0500
Kris Maglione wrote:
> On Mon, Nov 09, 2009 at 06:16:43PM -0600, tosh wrote:
> >unsubscribe
>
> For fuck's sake! It's not that hard, and we've just had this
> discussion. Well, I hope you can figure this one out yourself,
> or I suppose you'll have to stay sub
On Mon, Nov 09, 2009 at 07:20:28PM -0600, tosh wrote:
For fucks sake it's not that big of a deal is it? I don't read the
discussions, hence the unsubscribe. Gmail adds an unsubscribe link,
apparently it doesn't work. No need to be a dick.
It really is, given the frequency of these things, and t
On Mon, Nov 9, 2009 at 6:30 PM, Kris Maglione wrote:
> On Mon, Nov 09, 2009 at 06:16:43PM -0600, tosh wrote:
>
>> unsubscribe
>>
>
> For fuck's sake! It's not that hard, and we've just had this discussion.
> Well, I hope you can figure this one out yourself, or I suppose you'll have
> to stay sub
On Mon, Nov 09, 2009 at 06:16:43PM -0600, tosh wrote:
unsubscribe
For fuck's sake! It's not that hard, and we've just had this
discussion. Well, I hope you can figure this one out yourself,
or I suppose you'll have to stay subscribed.
--
Kris Maglione
Pessimists, we're told, look at a glas
unsubscribe
On Mon, Nov 09, 2009 at 04:47:00PM +0100, markus schnalke wrote:
> [2009-11-09 10:21] Kris Maglione
> > On Mon, Nov 09, 2009 at 04:02:56PM +0100, markus schnalke wrote:
> > >
> > >Aren't they able to take a look at the List-Unsubscribe header?
> >
> > Apparently. Look closely:
>
> > To: "dev+un
[2009-11-09 10:21] Kris Maglione
> On Mon, Nov 09, 2009 at 04:02:56PM +0100, markus schnalke wrote:
> >
> >Aren't they able to take a look at the List-Unsubscribe header?
>
> Apparently. Look closely:
> To: "dev+unsubscr...@suckless.org"
*LOL*
meillo
lto:dev+unsubscr...@suckless.org>
...
To: "dev+unsubscr...@suckless.org"
Subject: [dev] dev+unsubscribe
--
Kris Maglione
If you want to go somewhere, goto is the best way to get there.
--Ken Thompson
[2009-11-09 09:35] Kris Maglione
> On Mon, Nov 09, 2009 at 09:30:41AM -0500, Robert C Corsaro wrote:
> >dev+unsubscribe
>
> Annoying, isn't it? How many people do I have to manually
> unsubscribe?
Aren't they able to take a look at the List-Unsubscribe header?
meillo
On Mon, Nov 09, 2009 at 09:30:41AM -0500, Robert C Corsaro wrote:
dev+unsubscribe
Annoying, isn't it? How many people do I have to manually
unsubscribe?
--
Kris Maglione
For every complex problem there is an answer that is clear, simple,
and wrong.
--H. L. Mencken
dev+unsubscribe
This has also gotten too much for me . I hereby unsubscribe. Officially.
On Wed, Aug 19, 2009 at 4:40 PM, Nils wrote:
> You guys make me wanna unsubscribe, too. ;)
>
>
80 matches
Mail list logo
