Any chance of this set of patches being reviewed by someone with commit
privileges? Link to the thread for convenience since I'm cross-posting
to a different list: http://lists.suckless.org/dev/1504/26513.html .
Eric
On Sat, Aug 08, 2015 at 05:39:55PM +0200, Quolick wrote:
When I press Shift-Alt-Q, all windows killed without any confirmation.
Is there any patch to add some king of dialog box?
Maybe two menu items in the bar (like dmenu does) OK, Cancel?
You could make Shift+Alt+Q launch a shell script
This patch fixes a typo in dmenu.
Eric
From 98573e0f8c4dda3ebe2a3639f24046c7d80cc3d8 Mon Sep 17 00:00:00 2001
From: Eric Pruitt eric.pru...@gmail.com
Date: Wed, 5 Aug 2015 19:19:14 -0700
Subject: [PATCH] Fixed typo introduced by shared code
---
dmenu.c | 2 +-
1 file changed, 1 insertion(+), 1
On Fri, Jul 17, 2015 at 08:33:12PM +0200, Hiltjo Posthuma wrote:
patch 1: whitespace fixes
patch 2: make fp of type FILE * and use needed includes
patch 3: fix missing ;
You forgot the attachments.
Eric
I don't understand this patch. Mice don't have keys, they have buttons
(at least the dialects of English I'm familiar with). "Mouse keys" just
sounds wrong and confusing to me.
Eric
signature.asc
Description: Digital signature
Hi Klemens,
On Mon, Jan 11, 2016 at 05:29:47PM +, Klemens Nanni wrote:
> cc596365a (unbolify dmenu) "breaks" some of the patches provided at
> tools.suckless.org/dmenu/patches. Basically 's,bool,int' was all I had
> to do besides some offset correction. Since this is the first time I'm
>
On Sun, Jun 26, 2016 at 02:53:03PM +0200, Hiltjo Posthuma wrote:
> I have pushed the drw changes to dmenu and dwm.
>
> Thanks for the contributions!
>
> It would be nice if people test it and report any regressions with their
> setups
> (font-fallback specificly).
I'm in the process of merging
On Sun, Jun 26, 2016 at 02:53:03PM +0200, Hiltjo Posthuma wrote:
> It would be nice if people test it and report any regressions with their
> setups
> (font-fallback specificly).
I finished merging my changes with the upstream tree, and I have not
encountered any issues with fallback fonts while
On Sun, Apr 03, 2016 at 11:50:08PM +0200, Mattias Andrée wrote:
> That works with musl but not glibc.
If you use 'setlocale(LC_ALL, "")' with GCC, grep behaves as expected:
sbase$ echo äö | ./grep '[å]'
(1)
sbase$ echo å | ./grep '[å]'
å
Eric
On Mon, Aug 01, 2016 at 12:44:04PM +0200, Patrick Steinhardt wrote:
> ---
> dwm.suckless.org/patches/cfacts.md | 2 +-
> dwm.suckless.org/patches/dwm-6.1-cfacts.diff | 49
> ++--
> 2 files changed, 25 insertions(+), 26 deletions(-)
You generally don't need to
On Sun, Nov 27, 2016 at 08:43:20PM +0100, Ivan Delalande wrote:
> > Which GTK3 (sub)version and Firefox version do you use? Which other software
> > did you notice issues with?
>
> I've seen this problem only with Firefox, version 50.0 and the HEAD on
> mozilla-central.hg (52/53?) to debug the
I wasted an hour trying to figure out why st on different hosts using
the exact same terminfo configuration and statically compiled tmux was
displaying some text in yellow. The hosts where this produced yellow
text were using an Ubuntu-based Linux distro while the hosts where st
continued to work
On Fri, Dec 16, 2016 at 12:10:10AM +0100, Martin Kühne wrote:
> Wasn't there a patch about this at some point?
> When you use $repos, you tend to get older stuff.
I said nothing about using a precompiled st. If I did, I would submit
this to my repository maintainers, not this list.
Eric
On Sat, Nov 26, 2016 at 08:00:01AM +0100, Ivan Delalande wrote:
> This is mostly arg's 762b66a resurrected ("hack that adds
> NET_SUPPORTING_WM_CHECK handling..."), but we have to create a dedicated
> window which remains unmapped as bar windows can now be destroyed at any
> time with their
On Wed, Jan 04, 2017 at 08:33:12PM +0100, Markus Teich wrote:
> while fixing the focusonclick patch I noticed that the latest version on the
> wiki[0] breaks some mouse-bindings. After applying the patch to the current
> git
> master, I could not move or resize floating windows with the mouse
On Sun, Sep 10, 2017 at 04:31:24AM -0700, Eric Pruitt wrote:
> By setting the SIGINT handler with sigaction(2), automatic retries of
> the splice(2) syscall can be disabled by not setting SA_RESTART. This
> makes it possible to use Ctrl+C even if the "if" operand refers t
On Sun, Oct 08, 2017 at 01:01:55PM -0700, Michael Forney wrote:
> I am curious why ubase dd is using splice instead of just read/write
> (as you noted most other implementations do). Unless there is a big
> performance win, I would think that simplicity and portability would
> be preferable.
I
While testing a shell script with sbase and ubase, I ran into a problem
where dd would chew up my CPU whenever it read from a slow file. I
noticed this when running "dd" in a pipeline with "/dev/random" while my
system was low on entropy. Here are the timing outputs from ubase's dd
compared to GNU
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git Makefile Makefile
index 1c39fef..0e421e7 100644
--- Makefile
+++ Makefile
@@ -233,7 +233,7 @@ dist: clean
gzip sbase-$(VERSION).tar
rm -rf sbase-$(VERSION)
-sbase-box: $(LIB) $(SRC)
+sbase-box: $(LIB)
On Tue, Sep 05, 2017 at 09:31:04PM -0700, Eric Pruitt wrote:
> The amount of sys time spent by ubase's dd is always a lot higher than
> coreutil's even when the wall-clock time of the runs is comparable. I
> haven't spent a lot of time looking into this yet, so I don't have a
> pa
By setting the SIGINT handler using sigaction(2), automatic retries of
the splice(2) call can be disabled by not setting SA_RESTART. This makes
it possible to use Ctrl+C even if standard input is a terminal.
---
dd.c | 58 +-
1 file changed,
By setting the SIGINT handler with sigaction(2), automatic retries of
the splice(2) syscall can be disabled by not setting SA_RESTART. This
makes it possible to use Ctrl+C even if the "if" operand refers to the
controlling terminal. The SIGINT message has also been moved outside the
signal handler
On Sun, Sep 10, 2017 at 11:55:53AM +0100, Richard Ipsum wrote:
> This isn't a comment on this patch exactly, since this call exists in
> the existing handler, but unless I'm missing something about the way
> you're doing this it isn't safe to call fprintf in a signal handler
> since your signal
On Fri, Nov 03, 2017 at 12:14:46AM +0100, Laslo Hunhold wrote:
> However, as it has already been laid out numerous times, we can not
> accept companies to be in the list of contributors, only people. If
> you are interested in the reasons, I can lay them out again, but
> admittedly I think they
On Fri, May 18, 2018 at 12:12:32AM +0200, Michael Buch wrote:
> Nvm, that's the correct patch. Got confused by it auto-replying to the
> thread...
It didn't at least as far as Mutt is concerned. Are you using the Gmail
web UI? I think the Gmail web UI will treat emails with the same title
as part
On Thu, Mar 15, 2018 at 05:11:10PM +0100, Silvan Jegen wrote:
> The disadvantage of this is that you will have to save those
> attachments somewhere and then apply them. When using "git send-email"
> you can just feed the emails directly to "git am".
That depends on what email client you use.
On Thu, Mar 15, 2018 at 08:28:26PM +0100, Silvan Jegen wrote:
> > That depends on what email client you use. Mutt makes piping both whole
> > messages and individual attachments to arbitrary commands pretty
> > painless IMO.
>
> I use mutt as well but I don't know how to deal with attachments
On Thu, Mar 15, 2018 at 08:44:02PM +0100, Silvan Jegen wrote:
> Ah, I wasn't aware that the tags also work on attachments, neat. Thanks
> for the tip!
>
> That means both are equally convenient for me. However, if you send
> patches inline (not as attachments) commenting on specific parts of
>
On Thu, Mar 15, 2018 at 10:17:25PM +0100, Silvan Jegen wrote:
> Still sounds to me like having patches as attachments just causes me to
> have to change my default configuration though.
Change the world or change your configuration: the choice is yours! By
adding a handful of bytes to your Mutt
Since the default rule matching does substring comparisons, using the
fixed string "broken" as a fallback value can complicate or make
unambiguous matching impossible, so this change makes various fallback
strings for unset properties configurable via config.h.
---
config.def.h | 5 +
dwm.c
On Tue, Apr 03, 2018 at 02:07:37PM -0700, Eric Pruitt wrote:
> It seems odd to me that Git would create a broken (or perhaps
> backward-incompatible) patch because of that option. What version of Git
> are you using? I'm running 2.11.0.
Actually, the patch fails to apply for me, too
On Mon, Sep 24, 2018 at 10:16:31PM +0200, Ingo Heimbach wrote:
> I have recognized that a buffer size of 128*4 bytes is quite small to
> store base64 encoded clipboard content (see OSC52), especially when
> copying multiple code lines in a terminal editor like vim.
I agree that the current buffer
On Fri, Jan 25, 2019 at 11:44:43AM +0100, Hiltjo Posthuma wrote:
> Please don't send HTML mail to the list.
The message had text and HTML components. If you don't like HTML emails,
why not configure your client to prefer text/plain portions of
multipart/alternative emails?
Eric
On Sat, Mar 30, 2019 at 02:31:56PM +0100, Ryan Kes wrote:
> +int disableroman = 0;
> [...]
> + if (!disableitalic)
> + FcPatternAddInteger(pattern, FC_SLANT, FC_SLANT_ITALIC);
> + if (!disableroman)
> + FcPatternAddInteger(pattern, FC_SLANT, FC_SLANT_ROMAN);
I
On Mon, Apr 01, 2019 at 10:19:30PM -0700, Eric Pruitt wrote:
> On Sat, Mar 30, 2019 at 02:31:56PM +0100, Ryan Kes wrote:
> > +int disableroman = 0;
> > [...]
> > + if (!disableitalic)
> > + FcPatternAddInteger(pattern, FC_SLANT, FC_SLANT_ITALIC)
On Tue, Apr 02, 2019 at 08:15:21AM +0200, Ryan wrote:
> Feel free to change it. All I did with the patch is change the previous
> version so it works with 6.2.
I have no interest in the patch itself, just pointing out a problem I
saw.
Eric
On Wed, Jan 02, 2019 at 02:50:15AM +0100, kais euchi wrote:
> This article [0] made me wonder how to improve latency in st, and i
> thought i would share this small modification for a non-blinking setup.
> When blinktimeout is set to 0, it reduces latency by ca. 5ms [1] by avoiding
> useless delay
On Sat, Feb 16, 2019 at 01:05:41AM +0100, Igor Bukanov wrote:
> + { XK_Tab, ControlMask,"\033[1;5I", 0,0},
> + { XK_ISO_Left_Tab, ShiftMask|ControlMask,"\033[1;6I",0,0},
Are these escape sequences unique to Mintty? I wasn't able to find any
other emulators using
After upgrading my workstation to Debian 10, changes in Fontconfig
and/or DejaVu Sans Mono have changed the values of dc.font.height in my
st build. The characters themselves seem to be near pixel-perfect
matches. I "fixed" the problem by adjusting the chscale configuration
variable to shave a
On Sun, Mar 03, 2024 at 12:34:16AM +0100, Elie Le Vaillant wrote:
> +static void
> +tac(FILE *fp)
> +{
> + struct linebuf buf = EMPTY_LINEBUF;
> + struct line line;
> + getlines(fp, );
> +
> + if (buf.nolf) {
> + /* If the last line is not LF-terminated, the
> +
40 matches
Mail list logo