On Mon, May 7, 2018 at 9:36 AM Hiltjo Posthuma
wrote:
> No, documentation should be readable offline.
Even though BUGS *document* shortcomings, they're not really helpful as an
offline resource on their own, especially without the source to also
reflect them.
But please, move along, nothing to se
So you used savedconfig because it was mentioned in [0]?
cheers!
mar77i
[0] https://wiki.gentoo.org/wiki/St
You appear to be in a very unique dilemma. You have three different
pieces of the puzzle that don't fit together, as both the patch from
the site as well as my own branch fails for you. Then you hand off
your responsibility over which software version you use to your
distribution, but come to us to
I'm maintaining my copy of the patch on
https://github.com/mar77i/dotfiles/tree/master/abs/st-git
cheers!
mar77i
To gain control of what I paste into my terminal, I use a text editor.
Personally, I have never seen any leftover escapes (from either
website), but that may be because I'm really careful with selections.
cheers!
mar77i
Aren't we depending on Xft already?
https://stackoverflow.com/questions/9838385/replace-of-xkeycodetokeysym#22418839
cheers!
mar77i
The site is a wiki and you can search the git history like this:
http://git.suckless.org/sites/log/?qt=grep&q=azerty
If you're not willing to manually adjust a header file to your needs,
I wonder whether dwm is for you. Run xev and read
/usr/include/X11/keysymdef.h .
cheers!
mar77i
Urm, I'd prefer a local pointer, but I figure a modern compiler should
be perfectly capable of deciding that intermediate results and
pointers should be stored/cached for reuse. Which should sufficiently
illustrate that these particular lines of code are perfectly fine.
cheers!
mar77i
On Wed, Apr 5, 2017 at 6:24 PM, David Kennedy wrote:
> On every other system, I use my desktop as a sort of work area. I put stuff
> there that I need to do something with later, like notes and shortcuts to
> articles that I want to read. I see them every time I reboot or hide all the
> windows. I
Last time I checked, I liked dwm because it's KISS, somewhat like a potato.
Simple, yet unmatched in its versatility. Attachment to illustrate that.
cheers!
mar77i
...now now, don't hold contempt here. We're not one of *those* places.
cheers!
mar77i
The topic did come up in an earlier thread, though.
http://lists.suckless.org/dev/1610/30593.html
Thanks for trying to make st less surprising in this case.
cheers!
mar77i
Wasn't there a patch about this at some point?
When you use $repos, you tend to get older stuff.
cheers!
mar77i
On Mon, Dec 5, 2016 at 10:03 AM, Michael Forney wrote:
> This would eliminate the extra copies, but we still have the issue of
> doing fread repeated reads until the passed in buffer is completely
> filled before we are able to write anything. Run something like make
> 2>&1 | cat, and you will see
Sorry if this is completely off the hook now, but if FILE's buffering
is an issue here, can't we just setbuf(NULL)?
cheers!
mar77i
On Fri, Dec 2, 2016 at 9:53 PM, Bob Uhl wrote:
> Anyway, consider the patch withdrawn. If folks are maintaining their
> changes in config.h then it's obviously a terrible idea to obliterate
> it. I wouldn't submit a patch that I think makes things worse for
> folks.
Because you maybe you even w
Just keep your config.h and merge changes from config.def.h.
Why are you destroying a perfect system?
cheers!
mar77i
IMHO, when failing to parse command line arguments, usage() should be
called before exiting with EXIT_FAILURE.
on invocation with -h|--help, it should exit with EXIT_SUCCESS.
cheers!
mar77i
Run conway's game of life as your wallpaper [0].
make; ./life2d -r --conway
cheers!
mar77i
[0] https://github.com/mar77i/xdemos
Looking at the original mail again, please disregard. I've made a fool
of myself.
cheers!
mar77i
If I set st to dumping, I want it to dump to stdout, obviously. The
dumping in and on itself is not an error.
I suggest to instead add setbuf(stdout, NULL) at the top of the place
where the dump argument is parsed.
cheers!
mar77i
sizeof var (note the lack of parens) is a feature in c. It lets the
programmer put whatever type var is in one place and one place only.
The thing that got me away from putting parentheses to sizeof was
actually the fact that only in the absolutely rarest of cases (read:
never) you take the size of
666... for satan!
cheers!
mar77i
On Tue, May 24, 2016 at 7:11 PM, wrote:
> ...Ed, Sed, Awk...
Those are three different tools for more or less the same job. Eclipse
can do it already, so we don't need them in sbase.
cheers!
mar77i
24 matches
Mail list logo