On Thu, Oct 02, 2014 at 05:23:39PM -0700, Kartik Agaram wrote:
> > Here is a list of things I think are suckless-specific in practice:
FRIGN did cover it in detail but I'd like to point out some further
details that I've noticed.
> > - C code (most often) written in a plan9 like style.
If you wa
On Thu, 2 Oct 2014 17:23:39 -0700
Kartik Agaram wrote:
> > - Most often only one C file.
one C-file per program.
The most important part is forgotten though: We not only write mostly C,
but also try to use POSIX(01-08)-interfaces and established extensions.
Concerning the C-standard, we favor
On Thu, Oct 02, 2014 at 05:23:39PM -0700, Kartik Agaram wrote:
> I asked Quentin this off-list:
> > [...]
> > - No top-fucking-posting on the ML.
> > - Probably more, ask other people, even maybe on the ML.
> >
> [...]
>
> Can anybody think of other defining aesthetics? My addition: vehement
> disl
>> - One simple makefile, no GNU make.
What's the common denominator here? These are definitely non POSIX makefiles
-emg
I asked Quentin this off-list:
> > http://c9x.me/irc
> >
> > "Following suckless habits, I plan to provide some extensions as patches."
> >
> > I'm new here. Can you think of any pointers describing this and/or other
> > suckless habits?
And got back a great list:
> Here is a list of things I th
On Thu, Oct 02, 2014 at 04:47:48PM +0200, q...@c9x.me wrote:
> On Wed, Oct 01, 2014 at 04:03:34PM -0700, Eric Pruitt wrote:
> > I'm considering making a sic fork called "nssic" or "not so simple irc
> > client" and integrating libreadline or libedit.
>
> My post points to an existing project that i
On Wed, Oct 01, 2014 at 04:03:34PM -0700, Eric Pruitt wrote:
> > http://c9x.me/irc/.
> [...]
> I'm considering making a sic fork called "nssic" or "not so simple irc
> client" and integrating libreadline or libedit.
My post points to an existing project that is too close
to what you describe to b
On Wed, Oct 01, 2014 at 02:30:56PM -0700, Evan Gates wrote:
> Yes it does, but it's a horrible piece of code that desperately needs
> to be rewritten from the ground up along with pcw[0] and cw (in the
> pcw project). I haven't touched them in a long time because they work
> well enough for me when
On Wed, Oct 01, 2014 at 06:57:57PM +0200, q...@c9x.me wrote:
> how does rlwrap deal with random text that gets inserted by sic
> when some data arrives on the channel? This was my main problem
> with sic, to prevent that and enable multichannel I have written
> http://c9x.me/irc/.
I was originall
Hello,
On Wed, Oct 1, 2014 at 2:18 PM, Dmitrij D. Czarkoff wrote:
> random...@fastmail.us said:
>> It occurs to me that a "line input" program (that would work along the
>> lines of a mud client, with a separate editable input line from where
>> output goes, and maybe managing scrollback) would b
random...@fastmail.us said:
> It occurs to me that a "line input" program (that would work along the
> lines of a mud client, with a separate editable input line from where
> output goes, and maybe managing scrollback) would be a good candidate
> for a "do one thing" utility.
srw[1] apparently doe
On Wed, Oct 1, 2014, at 12:57, q...@c9x.me wrote:
> On Mon, Sep 29, 2014 at 09:55:07PM -0700, Eric Pruitt wrote:
> > rlwrap ./sic -h "$IRC_HOST" | tee -a irc-logs | grcat sic.grcat
>
> Hi,
>
> how does rlwrap deal with random text that gets inserted by sic
> when some data arrives on the chan
On Mon, Sep 29, 2014 at 09:55:07PM -0700, Eric Pruitt wrote:
> rlwrap ./sic -h "$IRC_HOST" | tee -a irc-logs | grcat sic.grcat
Hi,
how does rlwrap deal with random text that gets inserted by sic
when some data arrives on the channel? This was my main problem
with sic, to prevent that and ena
I started using sic as my IRC client, and I'd just like to share my
configuration. I have a script that invokes sic in a manner similar to
the following command:
rlwrap ./sic -h "$IRC_HOST" | tee -a irc-logs | grcat sic.grcat
With [rlwrap][1], I get familiar input handling, tee(1) gives me
lo
14 matches
Mail list logo
