Re: [dev] Stali RC

On 10/02/2015 10:21 AM, Richard wrote: - do we install a pager? I've look in bin for more/less/pg etc. Are there any plans for a pager? I looked in the TODO documents for both sbase and ubase but did not notice any. I am also curious about the pager.

[dev] Re: pager

On 10/04/2015 11:32 AM, Dimitris Papastamos wrote: Yes there are plans for a pager. I am curious why that is not listed in the TODO for sbase. The heirloom project has a pg implementation I think. 2425 lines: Heirloom pg http://heirloom.cvs.sourceforge.net/viewvc/heirloom/heirloom/pg/pg.c?

Re: [dev] [slock] Ctrl+Alt+Backspace Xorg Termination works

On 10/13/2015 06:03 AM, Jack L. Frost wrote: $ exec xinit As exec replaces your current shell's process, if xinit exits, you are thrown into the login prompt. That's good to know and clever. Thanks.

[dev] sbase: od: bug report

Since there is no accompanying patch/fix, I am using dev rather than hackers. Command od doesn't seem to like multiple file arguments. See attached. Script started on Mon 26 Oct 2015 10:48:54 AM EDT [greagle@T430-530GD sbase]$ git branch * master od-haskell [greagle@T430-530GD sbase]$ git pul

Re: [dev] sbase: od: bug report

On 10/26/2015 11:00 AM, Greg Reagle wrote: Command od doesn't seem to like multiple file arguments. See attached. I have been trying to debug this problem, but I haven't figured it out (yet). I have managed, however, to make reproducing the bug less verbose. See typescript. Scri

[dev] sbase: od: why avoid signed numbers?

Hello. As you probably already know, the standard specifies that type 'd' means signed decimal. I am curious about why: "the 'd' parameter for the [-t] flag is interpreted as 'u'" Given this difference, is od actually POSIX compliant?

Re: [dev] sbase: od: why avoid signed numbers?

On 10/27/2015 12:19 PM, FRIGN wrote: > ... we sometimes move away from POSIX where it seems to be necessary. Thanks for the explanation.

Re: [dev] dmenu segfaults when pressing control+enter without a selection

On 10/18/2015 06:46 AM, Markus Teich wrote: …and of course the always loved “update patches from the wiki to apply cleanly against git HEAD”. Just started to try to do so, and now I really understand why people hate stylistic source code changes. :>

[dev] a suckless hex editor

What do you think? I was afraid to overwrite the infile so I make the user specify an outfile. Maybe if I did better error checking it would be okay to overwrite? The user can choose to overwrite by specifying the same file for both infile and outfile. #!/bin/sh [ -z "$1" -o -z "$2" ] &&

Re: [dev] a suckless hex editor

Improved a little. Is it appropriate for inclusion in sbase? #!/bin/sh dump="xxd -g1" dedump="xxd -r" [ -z "$1" -o -z "$2" ] && { echo "$0 infile outfile"; exit 1; } [ -z "$EDITOR" ] && { echo "\$EDITOR must be defined"; exit 1; } tmpfile=$(mktemp) || exit 1 infile="$1" outfile="$2" $dump "$in

Re: [dev] a suckless hex editor

On 11/13/2015 11:45 AM, Alex Pilon wrote: xxd's provided by vim. As convenient as it is, should a "suckless hex editor" really depend on that? It should be the user's choice or not to install vim, regardless of anybody's feeling's on this list *either* way. Is there another tool that can do a r

Re: [dev] a suckless hex editor

On 11/13/2015 12:17 PM, Louis Santillan wrote: tr, bc & awk? Very cool. I'll see what I can do.

Re: [dev] a suckless hex editor

Okay then. It no longer depends on xxd. It depends on od for the hex dump (works with both GNU od and sbase od) and echo, awk, tr, cut for the reverse hex dump. #!/bin/sh [ -z "$1" -o -z "$2" ] && { echo "$0 infile outfile"; exit 1; } [ -z "$EDITOR" ] && { echo "\$EDITOR must be defined"; exit

Re: [dev] a suckless hex editor

On Fri, Nov 13, 2015 at 09:42:11PM +0100, pancake wrote: > Use rm -f I don't get it. Is this a Unixy geeky way of saying you don't like it?

Re: [dev] a suckless hex editor

On Fri, Nov 13, 2015 at 08:51:24PM +, Connor Lane Smith wrote: > On 13 November 2015 at 20:42, pancake wrote: > > Also, echo is a buildtin, so dont use absolute path for it > > My guess is the path was added because the builtin echo may not > support the -e flag. But that's because it's non-s

Re: [dev] a suckless hex editor

On Fri, Nov 13, 2015 at 07:54:07PM +0100, Nico Golde wrote: > I'm sorry to be blunt, but this is not a suckless hex editor, but a poor mans > hex editor that's barely useful for any real work in my opinion. I mean it > may > work fine for changing a single byte here or there and look at dumps, bu

Re: [dev] a suckless hex editor

On Sat, Nov 14, 2015 at 10:14:38AM -0500, Matthew of Boswell wrote: > He probably would have said "rm -rf" if he intended for you to delete > the project. At the end of your script, you have 'rm "$tmpfile"'. Got it. Thanks for explaining.

Re: [dev] [sent] 0.1 release

On 11/16/2015 07:18 PM, Stephen Whitmore wrote: On 11/17 00:38, Markus Teich wrote: I also remind you, that this is a developers list and not a user support list (suckless has no users, just developers). Just sending in bug reports without at least a proposal of how to fix it is seen as rude.

Re: [dev] [slcon2] Videos are now online!

On 11/13/2015 02:30 PM, FRIGN wrote: > videos of the slcon2 talks are now online[0] in the webm format. > > [0]: http://suckless.org/conference/ Great, thanks. Is there any code for "Simple Jabber - Divide And Conquer XMPP, Jan Klemkow"?

Re: [dev] [PATCH] Add libmill

On 11/19/2015 09:21 AM, Aditya Goturu wrote: > libmill rocks. Patch attached Wow, libmill looks really good, based on the tutorial, if it works as advertised.

[dev] sj: ucspi

Howdy. This is probably obvious to non-newbies so please don't make fun of me *too* much. Anyway, I can compile and run sj but it dies at this line in xmpp_init() if (write(WRITE_FD, msg, size) < 0) which refers to this: /* ucspi */ #define WRITE_FD 7 #define READ_FD 6 but these file

Re: [dev] sj: ucspi

I think I figured it out. I have to use it with tcpclient. Something like tcpclient jabber.org 5222 ./sj -u johndoe -s jabber.org perhaps.

Re: [dev] sj: ucspi

On 11/19/2015 02:54 PM, Matthew of Boswell wrote: Then I realized that of course, I need encryption... # tcpclient dukgo.com 5222 ./sslc ../sj/sj -u gnuman -s dukgo.com -r\ resources -d /home/matt/.xmpp What is sslc? Where do I get it?

Re: [dev] sj: ucspi

On 11/19/2015 03:02 PM, Greg Reagle wrote: > What is sslc? Where do I get it? Answering my own question: https://github.com/younix/ucspi

Re: [dev] sj: ucspi

On 11/19/2015 03:11 PM, Matthew of Boswell wrote: Note, however, that it did not work with sj. I think the reason is that xmpp port 5222 is a STARTTLS port, not a straight SSL port. Maybe that's why the example in the man page of sj uses port 5223, expecting that to be a straight SSL port.

Re: [dev] Re: [sbase] cal doesn't highlight current day

I don't think we need to discuss anything. I think what's missing is a patch. I think that a patch to highlight the current day would *probably* be accepted (but I have no authority, just a regular user/developer).

Re: [dev] [st] Reporting a Segmentation fault

That's right--buf is accessed without bounds checked. The problem is in ttyread() in the while loop, buf gets overflowed, i.e. ptr - buf exceeds BUFSIZ (8192). Haven't figured out how to remedy the problem (yet). On 11/20/2015 01:16 PM, Martti Kühne wrote: I can generally reproduce this reli

Re: [dev] [st] Reporting a Segmentation fault

On Sat, Nov 21, 2015 at 11:08:08AM +0100, Martti Kühne wrote: > What makes you think this is an overflow? Because the segmentation fault occurs when ptr goes past the end of buf.

Re: [dev] [st] Reporting a Segmentation fault

On Sat, Nov 21, 2015 at 06:57:30AM -0500, Greg Reagle wrote: > On Sat, Nov 21, 2015 at 11:08:08AM +0100, Martti Kühne wrote: > > What makes you think this is an overflow? > > Because the segmentation fault occurs when ptr goes past the end of buf. But you're right that bufle

[dev] sj: libressl

Hello. I am using Ubuntu 14.04. I assume that I need libressl/libtls in order for sj (tlsc) to work. It is not a package in the Ubuntu repositories. Where should I get it to build it?

Re: [dev] sj: libressl

On 11/23/2015 09:42 AM, Greg Reagle wrote: > Hello. I am using Ubuntu 14.04. I assume that I need libressl/libtls > in order for sj (tlsc) to work. It is not a package in the Ubuntu > repositories. Where should I get it to build it? To answer my own question: https://github.com

Re: [dev] sj

I did build thusly: installed version 1:0.88-3 of ucspi-tcp: http://packages.ubuntu.com/trusty/ucspi-tcp built and installed https://github.com/libressl-portable/portable cloned https://github.com/younix/ucspi, then commented out ERR_get_error and ERR_error_string, built, installed cloned

Re: [dev] sj

On 11/23/2015 11:34 AM, Jan Klemkow wrote: The tls certificate verification failed. Turn it off with the following environment variable: export TLSC_NO_VERIFICATION=1 That prevented the error message. It still doesn't seem to be working. Want to try to work on it together via IRC?

[dev] sj success!

It works! I am having a chat between Pidgin and sj. On 11/23/2015 12:23 PM, Jan Klemkow wrote: On Mon, Nov 23, 2015 at 11:40:35AM -0500, Greg Reagle wrote: On 11/23/2015 11:34 AM, Jan Klemkow wrote: The tls certificate verification failed. Turn it off with the following environment variable

[dev] dvtm: bug report: Mod-C

Mod-C Create a new shell window using the current working directory of the focused window. This is mod key followed by capital C. For me it does the same things as mod key followed by lower case c, i.e. it has no effect on the working directory of the new client window. For me this bug is

Re: [dev] dvtm: bug report: Mod-C

On 11/24/2015 06:59 AM, Greg Reagle wrote: Mod-C Create a new shell window using the current working directory of the focused window. This is mod key followed by capital C. For me it does the same things as mod key followed by lower case c, i.e. it has no effect on the working directory of

Re: [dev] dvtm: bug report: Mod-C

On 11/24/2015 09:31 AM, Greg Reagle wrote: And here is a fix attached. That doesn't work properly. Ignore it. Sorry.

[dev] scrollback with st

Hi Rashad. Welcome to the suckless community. Please note that the hackers@ list is for submitting patches, and dev@ is for general discussion [1]. Accordingly, I am replying to dev@. I recommend using dvtm [2] with st in order to get scrolling. Someone ought to change the FAQ. dvtm sucks cons

Re: [dev] scrollback with st

On 11/25/2015 03:58 AM, Ivan Tham wrote: > I would like to > use dvtm too but too bad, not support for true colors. If there is, > broadcast it to me so and I will switch to it. I don't know what you mean. Would you please elaborate?

Re: [dev] scrollback with st

On 11/25/2015 09:16 AM, Greg Reagle wrote: > On 11/25/2015 03:58 AM, Ivan Tham wrote: >> I would like to >> use dvtm too but too bad, not support for true colors. If there is, >> broadcast it to me so and I will switch to it. > > I don't know what you mean. Would

Re: [dev] c++ compiler that rocks

On Sun, Nov 29, 2015 at 12:59:32PM +0100, Rashad Kanavath wrote: > Hello Dimitris, > > I saw some mails on hackers list with subject line containing "scc". Since > then I looked into suckless page about the project. I took a wild guess > that it is "simple c compiler" > > But couldn't find a

Re: [dev] scrollback with st

On Sun, Nov 29, 2015 at 12:22:18PM +0100, Rashad Kanavath wrote: > My issue with the scrollback patches are below: > > 1. slow scrolling. FYI, I use dvtm for scrolling and it is plenty fast for me. I can hold down the shift and PageUp keys and it goes quite fast. > 2. when I have something prin

[dev] sj: explicit tlsc doesn't work

Thanks to the recent updates to sj[1] and ucspi-tools[2], sj is now easier to build. The man page for sj has this EXAMPLES tcpclient example.org 5223 tlsc sj -u user -s example.org but that doesn't work for me. I have to omit tlsc. It seems to be called automatically. Am I doing somet

[dev] debugging sj

I don't experience any bugs in sj, but I would like to see the raw XML messages that are sent back and forth via sj, messaged, iqd, and presenced, in order to be able to understand better. These programs write to "in" files (named pipes). So what is the best (easiest, most convenient) way to get

Re: [dev] debugging sj

On 12/01/2015 10:55 AM, Greg Reagle wrote: I don't experience any bugs in sj, but I would like to see the raw XML messages that are sent back and forth via sj, messaged, iqd, and presenced, in order to be able to understand better. These programs write to "in" files (named pipe

Re: [dev] debugging sj

On 12/04/2015 12:57 AM, Jan Klemkow wrote: I wrote ucspi-tee[1] to do this job for me. But I think there is a similar tool of djb's tool chain, that does it, too. Okay yes I can compile and run your program ucspi-tee. But how exactly do I use it? This is how I (successfully) use sj now:

[dev] sj: bug in receiving presence

In this message, I point out the error and state the correct way of receiving presence. FRIGN, please don't call me a help vampire. :> I do plan to write the patch, but it might take me a little while. Re: https://github.com/younix/sj in presenced.c in recv_presence(), lines 254-255 stat

Re: [dev] sj: bug in receiving presence

I fixed the problem. I want to clean up and test my modification some more before I submit it.

Re: [dev] suckless bignum library

On 12/10/2015 12:57 PM, FRIGN wrote: What does the base have to do with the results? A lot. For instance, "Many non-integral values, such as decimal 0.2, have an infinite place-value representation in binary (.001100110011...) but have a finite place-value in binary-coded decimal (0.0010).

Re: [dev] interest in development of suckless project

On 12/10/2015 12:10 PM, Rashad Kanavath wrote: I am interested to join the suckless development efforts. It will be a pleasure to waive some of my leisure time into this because I like suckless tools and its philosophy. Could someone provide me any guidance or directions? Did you see h

Re: [dev] sj: bug in receiving presence

On 12/09/2015 07:10 PM, Jan Klemkow wrote: I committed your diff for presenced with a following clean up. But maybe, I will change the presenced semantic a bit. But for the moment I fixes the daemon in a very good way. Thanks for your help! My pleasure. Changing the semantics in what way?

Re: [dev] advised surf-webkit2 dependency versions

On Fri, Dec 11, 2015 at 10:21:39AM +, Dominykas Mostauskis wrote: > I am running Debian Stable, so it is very likely that my libraries are > outdated. I already had problems compiling, due to webkit2gtk being > too old, and runtime warnings due to soup being too old. I use surf successfully on

[dev] st: keys and infocmp

Hello. If there are any man pages or articles or FAQs about this topic that would be good to read, please refer to them. Running Xubuntu 12.04 and the latest st on a ThinkPad laptop, these are the results I get, correlated with the results of infocmp. I got the output from the keys by running c

Re: [dev] st: keys and infocmp

On 12/14/2015 01:05 PM, Greg Reagle wrote: Running Xubuntu 12.04 and the latest st on a ThinkPad laptop, these are Sorry, that's Xubuntu 14.04.

Re: [dev] Font edition tooling

On 12/23/2015 09:54 AM, Mattias Andrée wrote: > I would argue you not to use public domain because > of its legal status. In most non-English speaking > countries you cannot release something as public > domain. I agree. I suggest a simple permissive license such as the one used for X11 [1] or E

Re: [dev] A replacement for at.

On Fri, Jan 01, 2016 at 06:05:58PM +0100, Kamil Cholewiński wrote: > Yes, please let's stop writing process management code into daemons and > instead solve this problem in a portable and non-sucky way. It's called runit: http://smarden.org/runit/

[dev] announcing Simple Jabber Tools

https://github.com/GReagle/sjt The Readme explains it: https://github.com/GReagle/sjt/blob/master/Readme.md or see attached # sjt - Simple Jabber Tools ## Summary User interfaces for simple jabber. An attempt to produces some easy-to-use front ends for simple jabber. Of course it depends on a

[dev] automating running and building

In the same spirit as my previous post about automating with entr ... I would love to be able to have some way for running a compiled C program that automatically runs make on the program before actually running the program. Of course I don't want all of my programs to work this way, but when

Re: [dev] Auto-preview man pages

On Fri, Jan 08, 2016 at 12:50:14AM +0100, hiro wrote: > i don't need preview any more. i just write the content and expect it > to show up right. Perhaps one day I will reach your level of enlightenment. :>

Re: [dev] Auto-preview man pages

On Thu, Jan 07, 2016 at 01:56:13PM -0500, Greg Reagle wrote: > Here is what I figured out using entr: I run > ls address.yaml | entr make address.pdf > which means I don't have to type make, and I run > ls address.pdf | entr -r mupdf /_ > which means I don't have to

Re: [dev] Auto-preview man pages

On Fri, Jan 08, 2016 at 12:31:34AM +0200, Adrian Grigore wrote: > On Thu, Jan 7, 2016 at 8:56 PM, Greg Reagle wrote: > > I find it a real pain to work with things like man page source and markdown > > source and so forth because of the extra steps of making the output/object >

Re: [dev] automating running and building

On Thu, Jan 07, 2016 at 05:22:38PM -0800, Louis Santillan wrote: > Do mean something like this in a makefile? Essentially adding a > `./$@` to end of `dwm` target: I tried it and it does not seem to be a solution. If dwm is up to date, Make won't run the recipe and ./$@ won't be run. So you hav

Re: [dev] automating running and building

On Fri, Jan 08, 2016 at 12:53:26AM +0100, hiro wrote: > are you asking how to compile "make program; program" into a C program? Hi Hiro. I don't know whether you are being serious or joking but that gives me an idea which might be a solution. Let's say that it is the cal program that I want to b

Re: [dev] Auto-preview man pages

On Thu, Jan 07, 2016 at 09:20:06PM +0100, Roberto E. Vargas Caballero wrote: > On Thu, Jan 07, 2016 at 01:56:13PM -0500, Greg Reagle wrote: > > I find it a real pain to work with things like man page source and markdown > > source and so forth because of the extra steps of making th

Re: [dev] Auto-preview man pages

On Fri, Jan 08, 2016 at 06:42:21AM +0200, Adrian Grigore wrote: > On Fri, Jan 8, 2016 at 5:05 AM, Greg Reagle wrote: > > echo Readme.md | entr sh -c 'markdown Readme.md | w3m -T text/html' > > > > Still not ideal, because you have to quit from w3m manually. If

Re: [dev] Auto-preview man pages

On Fri, Jan 08, 2016 at 12:53:56AM -0500, Greg Reagle wrote: > If you use the -r option of entr, then you do get complete and very > satisfying automation when running a GUI. For instance this works great: > echo Readme.md | entr -r sh -c 'mkd2html Readme.md ; netsurf Readme.html&

Re: [dev] [PATCH] Reload on SIGHUP

On 01/09/2016 02:18 PM, Charles Lehner wrote: This patch makes surf reload its pages when it receives a SIGHUP signal. This makes it easier for shell scripts to trigger surf to reload. Excellent. This makes it possible to use it with entr without killing and restarting. Fellow hackers, should

[dev] another text user interface for sam

I value the intelligence and wisdom of this community, so I'd like to know what you think of this idea. Has it already been done? Are there disadvantages that I don't realize? Thanks. I recently learned the text editor sam[1] and I like it and I think that Structural Regular Expressions are

Re: [dev] another text user interface for sam

On 02/26/2016 10:56 AM, Connor Lane Smith wrote: In any case, if there*were* an attempt, with more manpower, either to reverse engineer the binary sam protocol or to implement a new editor, then I'd be very happy to lend a hand. Thanks for your thoughtful reply. What about a third option: use

Re: [dev] another text user interface for sam

On 02/26/2016 11:29 AM, Raphaël Proust wrote: I find the supposed “transparency” of changes in a group is often buggy. I.e., when using something like ,x/ I got it to work for me: cat test | ssam ',x/start/ { i/\\texttt{/ a/}/ }' Apparently there is no need to backslash-escape the braces since

[dev] quirks with sam's structured regexps

On Sun, Feb 28, 2016 at 11:34:37AM +, Raphaël Proust wrote: > I managed to reconstruct an example that I am dissatisfied about. > The following works: > Edit ,x/test/{ > i/< > a/> > } > But not the following: > Edit ,x/test/{ > a/> > i/< > } > The second one you the result "t" and a warning abo

Re: [dev] another text user interface for sam

On 02/26/2016 11:52 AM, Connor Lane Smith wrote: Anyway, that could work. If we were to do that then I'd suggest we first rip out all of sam's mesg and rasp code and work from there. The code for the command line interface ought to stay. Such a UI likely won't have some features one might really

Re: [dev] quirks with sam's structured regexps

On Tue, Mar 01, 2016 at 07:59:41AM +, Raphaël Proust wrote: > On 28 February 2016 at 17:20, Greg Reagle wrote: > > I get these results: The first version works fine. The second version > > shows error "?changes not in sequence" and does nothing. > > There

Re: [dev] quirks with sam's structured regexps

On 03/01/2016 11:39 AM, Raphaël Proust wrote: On 1 March 2016 at 12:43, Greg Reagle wrote: That's interesting. It's funny that sam does a better job since acme is a successor to sam. I wonder if/how they share code. I don't know if they do. The man page for acme referenc

Re: [dev] another text user interface for sam

On 03/02/2016 07:42 AM, Connor Lane Smith wrote: > On 2 March 2016 at 10:40, Maxime Coste wrote: >> That has been provided by Kakoune for a looong time I have never heard of Kakoune. Thanks for informing me of it. > Not as long as I've wanted it! > > (My first rant on this mailing list about '

Re: [dev] another text user interface for sam

On 03/02/2016 10:45 AM, Maxime Coste wrote: > How does sam handles parallel grouping when we get multiple incompatible > changes > to the same range of text ? It looks like it refuses. Using `sam -d` from 9base, the following command: x/echo/ { c/AAA c/BBB } produces error message "?changes no

Re: [dev] another text user interface for sam

On 03/02/2016 11:22 AM, Connor Lane Smith wrote: > On 2 March 2016 at 16:06, Greg Reagle wrote: >> Well sam has ISRE, but it lacks a nano/vi/emacs-like (full screen >> interactive) TUI. > > I think the key to *interactive* structural regular expressions is > that it must

[dev] Lessons Learned from 30 Years of MINIX

http://cacm.acm.org/magazines/2016/3/198874-lessons-learned-from-30-years-of-minix/fulltext The connection to suckless is that the author has strong minimalist and anti-bloat tendencies.

[dev] ways of viewing application indicators

Greetings. I switched over to dwm recently on one of my computers. I was using XFCE (Xubuntu) before. I needed to get to the dropbox GUI to change some settings. I got it working with `dbus-launch xfce4-panel &`. So now I can see the application indicators including Dropbox. But it's not

Re: [dev] ways of viewing application indicators

On 03/14/2016 01:13 PM, Hannes Blut wrote: > On 14.03.16 at 12:53pm, Greg Reagle wrote: >> But it's not ideal. The XFCE panel acts a bit screwy. Are there other ways >> to get access to the application indicators? > > Maybe have a look at http://dwm.suckless.org/patch

Re: [dev] structural regular expression support for vis

> On 27 March 2016 at 09:16, Marc André Tanner wrote: > > Did anyone else participating in this thread (Connor?, Greg?) bother > > to give it a try? I did not because I don't know vi. I usually use Emacs and sometimes nano. I learned sam recently. Well, I've looked at vi before but I just don'

Re: [dev] [st] possible bug with unicode character

No problem here. I am using st with: static char font[] = "Liberation Mono:pixelsize=15:antialias=true:autohint=true";

[dev] a few questions about watch in ubase

Please excuse me if these questions are rudimentary. I am using Debian Stable. Why is watch linked with the crypt library? cc -s -o watch watch.o libutil.a -lcrypt It does not seem to need it. watch uses "\x1b[2J\x1b[H" to clear the screen, which are the two control codes Erase Screen and C

Re: [dev] a few questions about watch in ubase

Thank you to Dimitris and Ryan for answering my questions--very informative. On 04/21/2016 02:04 PM, Greg Reagle wrote: Please excuse me if these questions are rudimentary. I am using Debian Stable. Why is watch linked with the crypt library? cc -s -o watch watch.o libutil.a -lcrypt It

Re: [dev] [question] Does bash suck?

On 04/23/2016 09:38 AM, Kamil Cholewiński wrote: I don't like rc since there are two incompatible implementations, one is the real thing and the other is actually usable for interactive use. I like Plan 9's rc a lot, for scripting. I don't think it sucks at all. I think it is good and more e

Re: [dev] [question] Does bash suck?

On 04/23/2016 01:53 PM, Kamil Cholewiński wrote: Make that two, quoting the man page: The list flattening operator, $^foo, is spelt $"foo in those versions of the Bell Labs rc which have it. No, rakitzis's rc accepts both syntaxes. That's why I didn't submit an issue for it. All other in

[dev] execline shell

On 04/23/2016 07:49 PM, ra...@openmailbox.org wrote: execline works on a different concept than regular shells: http://skarnet.org/software/execline/grammar.html Execline looks interesting, but I don't quite comprehend it. How would a script such as the following be written in execline? #!/

Re: [dev] a few questions about watch in ubase

On 04/25/2016 02:11 PM, k...@shike2.com wrote: Dimitris, if I send patches to remove these hard coded sequences by calls to tput the patches will be accepted? On my computer, tput comes with package "ncurses-bin". Is that an appropriate dependency for ubase?

Re: [dev] execline shell

On 04/24/2016 10:38 AM, Kamil Cholewiński wrote: execline is not exactly a shell. It's supposed to facilitate "DJB-style" command chaining, and focuses on little else. Suppose you have a bunch utilities that each do exactly one thing, and then 'execve(2)' the remainder of their arguments:

[dev] dmenu and dwm: is exec really needed

I use dwm. Sometimes I use Mod-p to start a GUI program like firefox. I looked at the output of ps xf and noticed that my shell is sticking around: 21347 ?S 0:00 /usr/bin/fish 21388 ?Rl 0:04 \_ iceweasel I can type `exec firefox` instead of `firefox` to avoid this, bu

Re: [dev] [lnanosmtp]

On 06/09/2016 01:35 PM, FRIGN wrote: On Thu, 9 Jun 2016 19:18:21 +0200 Markus Wichmann wrote: Hey Markus, Dear Lord, it's been a while since I've seen such nice code make so bafflingly bad design choices. Where to start? the suckless mailing list is not a place for religious cults. 1. The

Re: [dev] [st] Latest git - Nano with syntax highlighting strange bug

On Sun, Jul 17, 2016 at 10:45:10PM +0200, hadrien.lac...@openmailbox.org wrote: > I've recently changed from urxvt to st and noticed a bug when using nano > which will be easier to describe with a short gif: > https://a.cocaine.ninja/xtlajf.gif > This issue happens ONLY when I change "static unsi

Re: [dev] [dwm] Crash when setting window title to a single emoji

I cannot reproduce it on my computer.  Using Debian 8.5, dwm commit 7af4d439bdb5a2e40aca69446a3367bd71431c45 (which is behind the latest), xserver-xorg  1:7.7+7

Re: [dev] Re: [dwm] Crash when setting window title to a single emoji

On Wed, Aug 31, 2016, at 09:29 AM, Markus Unterwaditzer wrote: > Here's another one that fails: > >     PROMPT_COMMAND='echo -ne "\x1b]0;\xf0\x9f\xa4\x94\x07"' Well it shows up for me as a sort of inverse (foreground and background switched) question mark, but no malfunction, and this is from con

Re: [dev] Re: [dwm] Crash when setting window title to a single emoji

On Wed, Aug 31, 2016, at 01:05 PM, Markus Unterwaditzer wrote: > Greg, the issue only appears to me if I install bdf-unifont from > [extras]. Okay. I don't have that package available on Debian 8.5. Would any of these be appropriate? greg@t400 ~> acseno bdf bdfresize - tool for resizing BDF form

Re: [dev] Re: [dwm] Crash when setting window title to a single emoji

On Wed, Aug 31, 2016 at 08:59:05PM +0200, Markus Unterwaditzer wrote: > Hello Greg, > > I think the `unifont` package is it. For comparison, this is the content of > the > bdf-unifont package on ArchLinux: > > /usr/ > /usr/share/ > /usr/share/fonts/ > /usr/share/fonts/misc/ >

Re: [dev] Shell style guide

On Tue, Sep 6, 2016, at 03:27 PM, Evan Gates wrote: > Sadly there is a lot of software these days that requires bash. > Hopefully we can avoid most of it, but I'm sure it'll pop up now and > then. I'd say anything that can't be done well/safely in sh should be > done in rc, but bash is ubiquitous.

Re: [dev] Shell style guide

On Tue, Sep 6, 2016, at 08:23 PM, Adrian Grigore wrote: > What do you think of camelCase names for functions/variables? Fine with me. I don't have a_strong_preference forEitherStyle.

Re: [dev] Shell style guide

On Thu, Sep 8, 2016, at 10:05 AM, Kamil Cholewiński wrote: > Wow, shell quoting is just fucked up crazy. I was mostly using unquoted > $@ my whole life. And here I thought I knew enough not to screw up a > simple script, It is common knowledge to always double-quote $@, i.e. "$@", in Bourne/Posix

Re: [dev] Shell style guide

On Thu, Sep 8, 2016, at 10:11 AM, Greg Reagle wrote: > On Thu, Sep 8, 2016, at 10:05 AM, Kamil Cholewiński wrote: > > Wow, shell quoting is just fucked up crazy. I was mostly using unquoted > > $@ my whole life. And here I thought I knew enough not to screw up a > > simp

<    1   2   3   4   >