commit c58eb2ceb965785dbe9fecb688e10250d17aeca7
Author: Laslo Hunhold
AuthorDate: Mon Aug 29 10:30:00 2022 +0200
Commit: Laslo Hunhold
CommitDate: Mon Aug 29 10:30:00 2022 +0200
Quote input variables
The passed values can be expected to never contain spaces, but it's
bet
commit 6e6c538e4efb4d191a2f0391466556eb758d76bd
Author: Laslo Hunhold
AuthorDate: Mon Aug 29 10:31:54 2022 +0200
Commit: Laslo Hunhold
CommitDate: Mon Aug 29 10:31:54 2022 +0200
Use parameter expansion of variables within heredoc
Thanks to Quentin Rameau and Thomas Oltmann f
On Sun, 28 Aug 2022 20:00:42 +0200
Quentin Rameau wrote:
Dear Quentin,
> But of course, that's why the construction ${variable} exists,
> for this very common case.
> It's clear that UNITs isn't a variable,
> so you need to separate the variable from the string.
> You don't that with a subshell
Either is guaranteed to exist by POSIX, as opposed to ~/tmp.
---
surf-open.sh | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/surf-open.sh b/surf-open.sh
index c22edc2..4dfce4a 100755
--- a/surf-open.sh
+++ b/surf-open.sh
@@ -3,7 +3,7 @@
# See the LICENSE file for copyright
---
surf-open.sh | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/surf-open.sh b/surf-open.sh
index 4dfce4a..446b3a4 100755
--- a/surf-open.sh
+++ b/surf-open.sh
@@ -1,6 +1,6 @@
#!/bin/sh
#
-# See the LICENSE file for copyright and license details.
+# See the LICENSE file f
If a trailing `%' character occurs, we read past the end of the format
string and thus introduce UB. Reproducible by executing the following:
./printf %
This happens because the format string here actually consists of two
characters, `%' _and_ the trailing nul-byte. The flag parsing loop
matches
From: explosion-mental
no need for `i` so remove the i variable.
:gigachad:
---
dwm.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/dwm.c b/dwm.c
index e5efb6a..c2dcb15 100644
--- a/dwm.c
+++ b/dwm.c
@@ -280,7 +280,6 @@ void
applyrules(Client *c)
{
const char