On 6.2.2023 1.39, Adam Price wrote:
tsetattr(csiescseq.arg, csiescseq.narg);
break;
- case 'n': /* DSR – Device Status Report (cursor position) */
- if (csiescseq.arg[0] == 6) {
+ case 'n': /* DSR – Device Status Report */
+
On 20.11.2022 16.58, Tom Schwindl wrote:> I don't quite get why there is
a variable argument list instead of just using
a single argument which contains the prompt. I can't see the need for formatting
in a y/n prompt. I also wouldn't use `nomsg' since it just polutes stderr.
The specification
On 19.11.2022 23.46, Alan Potteiger wrote:
diff --git a/mv.c b/mv.c
index 8441f9c..51efde5 100644
--- a/mv.c
+++ b/mv.c
@@ -49,6 +57,9 @@ main(int argc, char *argv[])
ARGBEGIN {
case 'f':
break;
+case 'i':
+mv_iflag = 1;
+
On 24.10.2022 13.01, NRK wrote:> But which approach to take is the
maintainer's call, not mine.
I've attched both fixed-size and dynamic-allocation patch (but
simplified without goto).
The dynmaic[sic] version incorrectly passes sizeof(buf), where buf is
char *, as the size of buffer in the
On 2.9.2022 23.38, NRK wrote:
`ssize_t` is bit of an exotic type. by POSIX, it's only guaranteed to be
able to hold {-1, SSIZE_MAX} [0], meaning that negative values less than
-1 isn't guaranteed to representable in `ssize_t` (though it works out
in practice).
by default `ctrl+u` will call
On 2.9.2022 14.01, g...@suckless.org wrote:
commit 528d39b011afb7ef6fd794ba6b74155d4e69bc68
dmenu.c b/dmenu.c
index 969f6d8..6b285df 100644
--- a/dmenu.c
+++ b/dmenu.c
@@ -517,9 +517,9 @@ insert:
case XK_Tab:
if (!sel)
return;
-
Make fgetrune() put the breaking byte back, if it was not the only one
read, as this may be the start of the next, valid, rune.
Also consider erroneous runes to break a valid sequence, otherwise there
will be false-positive matches.
---
libutf/fgetrune.c | 3 +++
strings.c | 4 +---
2
On 9.4.2022 13.51, Hiltjo Posthuma wrote:
I've heard similar reports with monitor plugging and unplugging not working
nicely.
Can someone test this patch and report back these conditions or if it improves
things?
FWIW I've been using this change ever since I submitted it, and plug and
When monitors are removed, the coordinates of existing monitors may
change, if the removed monitors had smaller coordinates than the
remaining ones.
Remove special case handling so that the same update-if-necessary loop
is run also in the case when monitors are removed.
---
dwm.c | 68
Build on auto-sync and only mark window dirty on palette changes and let
the event handler do the actual draw.
---
st.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/st.c b/st.c
index 51049ba..c71fa06 100644
--- a/st.c
+++ b/st.c
@@ -1927,7 +1927,7 @@ strhandle(void)
10 matches
Mail list logo