Re: [dev] Learn C
Yo. Maybe you wanna read this? https://git.suckless.org/ https://9p.io/sources/plan9/sys/src/cmd/ Regards Robin. On Sun, 24 Mar 2019 at 11:29, Thuban wrote: > > Hi, > I want to learn C. I mean, sane C. > What i read before was based on big IDE such as codeblocks. So, I don't > know how to write Makefiles from scratch. (just an example). > As an example, I found gobyexample [1] great. But it's go. > Any reading advice? > > Thanks. > Regards > > [1] : https://gobyexample.com/ > -- > thuban >
Re: [dev] [surf] copying to clipboard instead of primary
Hi. Does this help? https://developer.gnome.org/gdk3/stable/gdk3-Selections.html https://git.suckless.org/surf/file/surf.c.html#l1817 Regards Robin. On Tue, 8 Jan 2019 at 18:37, Caio Barros wrote: > > Hello, > > For some time I've been struggling with clipboard selection on surf. > It seemed to me that it was inconsistent: if i used the mouse do copy > text it worked, but Ctrl-c didn't seem to always work. After trying to > use Ctrl-y to copy the current URL I noticed that I could paste it > using the middle mouse click, but not using, for instance Ctrl-Shift-V > in st. > > After digging a little bit I finally discovered the difference of > PRIMARY and CLIPBOARD selections in X[1]. So, if I understand > correctly, using Ctrl-C or Ctrl-y in surf copies text to PRIMARY, is > that right? If so, my question is how to either change this behavior > of surf or consistently paste text copied to the PRIMARY selection > using the keyboard instead of the middle mouse click? > > If what I'm seeing is not the expected behavior, then what should it > be? I'm not sure if this is related but I noticed that if I type > Ctrl-Shift-o to open the Inspector nothing happens. > > Thanks! > Caio > > [1] https://wiki.archlinux.org/index.php/Clipboard >
[dev] [announcement] jack_patchbay: ncurses patchbay for jack
Hi. I made a software: https://gitlab.com/byllgrim/jack_patchbay "Terminal (ncurses) patchbay for jack audio connection kit, written in C89, used to connect ports of jack clients." It's very minimal so maybe some of you people are interested. Regards Robin.
Re: [dev] Coding style: why /* */ and not //?
That is a rather bold sentiment. At uni the attitude is opposite - I actually saw home assignments stating "remember to use many comments to make the code more readable". I actually agree with you; there is much less clutter if the comments don't duplicate that which is already communicated through good naming, and the code is more readable when good naming makes comments superfluous. On Wed, 26 Dec 2018 at 21:57, Bobby Powers wrote: > > On Wed, Dec 26, 2018 at 10:44 AM wrote: > > Preprocessor. I guess having 2 ways to define comments is not significant, > > then better stick to one and the historical one. > > Better than one way is zero ways -- comments are not semantically > significant, so rather than argue about which standards-defined > comment style to use it would better to ban them all. >
