On Thu, 2 Feb 2017 20:42:06 +0100
Josuah Demangeon wrote:
> I started such a tool recently. It is probably not
> suckless, as it is already 1600 loc, but can properly
> display a man page, colour escape codes and content from
> UTF-8-test.txt and UTF8-demo.txt without ncurses.
>
> http://github
I really liked the idea of st, but the alternate cursors don't
work well without blinking--too hard to spot. Attached is my
first attempt at adding code to a suckless project, comments
welcome.
Thanks,
Andy Valenciadiff --git a/st.c b/st.c
index fbcd9e0..4e7ab10 100644
--- a/st.c
+++ b/st.c
@@ -1
On Fri, Feb 03, 2017 at 10:00:37AM +, Raphaël Proust wrote:
> On 2 February 2017 at 17:46, Marc André Tanner wrote:
> >Sam supports a count specifier: s2/pattern/replacement/ only replaces
> >the second occurrence of pattern. This is currently not supported but
> >can be mimicked u
On Fri, Feb 03, 2017 at 04:29:10PM +0100, Tobias Girstmair wrote:
> I don't know what to say to you: No, it doesn't.
> (I believe this to be a bug?)
I believe you are conflating the behavior of dmenu and dmenu_run.
dmenu returns "jj s" with success exit code, like the man page says it
will. dmen
I don't know what to say to you: No, it doesn't.
(I believe this to be a bug?)
On Fri, Feb 03, 2017 at 03:35:36AM +0100, Quentin Rameau wrote:
> > That's interesting. It doesn't do what you (and the man page; missed
> > that, mea culpa) described
>
> Yes it does.
>
On 3 February 2017 at 10:00, Raphaël Proust wrote:
> One thing that always bothers me with regexes is that the same syntax
> (parens) is used for both overriding precedence (e.g., `(foo)*` to
> specify that star operates on the sequence `foo`) and groups (to be
> recalled with `\1`–`\9`).
>
> Anyo
On 3 February 2017 at 10:00, Raphaël Proust wrote:
> On 2 February 2017 at 17:46, Marc André Tanner wrote:
>> […]
>> * Multi file support is not really well supported:
>>
>> - The X and Y commands currently operate on windows, not files.
>> Meaning that if a file is being displayed in
Willy Gfn wrote:
> Michael Forney wrote:
> > On 12/24/16, Cág wrote:
> > > Markus Wichmann wrote:
> > >
> > >> Well, that looks like it might be problematic, doesn't it? Especially
> > >> when you find out, that the size of h->name there is 100 bytes. path
> > >> contains, of course, the entire fi
Michael Forney wrote:
> On 12/24/16, Cág wrote:
> > Markus Wichmann wrote:
> >
> >> Well, that looks like it might be problematic, doesn't it? Especially
> >> when you find out, that the size of h->name there is 100 bytes. path
> >> contains, of course, the entire file path relative to the startin
Michael Forney wrote:
> On 2/2/17, willy wrote:
> > At this point, I'm not sure where to look at, or even if the bug
> > really lies in tar and not in bzip2.
> > I checked the size (both octal and converted) and the value is good. So
> > I'm not sure why the headers are not well read.
> > In the c
Mattias Andrée wrote:
> I'm not convinced mk(1) is less sucky
> than POSIX make(1), but it may be less
> sucky than many make(1) implementations.
There is also bmake(1)[0], a port of NetBSD's
make(1)[1]. OpenBSD has their own
make(1)[2] as well.
Cág
[0]:
http://www.crufty.net/help/sjg/bmake.ht
On Thu, Feb 02, 2017 at 06:45:49PM +0100, Mattias Andrée wrote:
> I'm work on implementing make(1)
In theory, linux kbuild should be a good reference for the minimum set of
makefile extensions to code. Well, in theory, the guys paid full-time at the
linux fondation to work on kbuild, should have c
On 2 February 2017 at 17:46, Marc André Tanner wrote:
> […]
> In the meantime lots of bugs have been fixed. I would like to encourage
> all sam/acme users who are also somewhat familiar with vi(m) to try out
> current master of vis and report back on their experience:
>
> https://github.com/mart
13 matches
Mail list logo
