Hi Mikhail,
> Colon-separated SGR (new version; ':' is the legacy one)
Could explain a bit more what this patch is about,
with some context and telling the goal?
On Tue, Apr 02, 2024 at 09:41:15PM -0400, DOGMAN wrote:
> With this patch, st will reset its window title when an empty string is
> given as the terminal title. For example:
> printf "\033]0;\007"
>
> Some applications, like termdown, expect this functionality. xterm
> implements it, but it
On Sat, Mar 30, 2024 at 01:59:28AM +0100, Storkman wrote:
> On Fri, Mar 29, 2024 at 07:27:43PM +0100, Hiltjo Posthuma wrote:
> > On Wed, Mar 27, 2024 at 04:11:27PM +0100, Storkman wrote:
> > > On Sun, Feb 25, 2024 at 11:57:03AM +0100, g...@suckless.org wrote:
> > > > commit
On 24/03/30 01:59AM, Storkman wrote:
> For a specific example, copy text followed by a wide glyph into bash
> or mksh, e.g.
> A字
> and press backspace once. Both characters will be erased.
Or, when using tmux, split vertically, then in the right pane copy the above
text and press left
On Fri, Mar 29, 2024 at 07:27:43PM +0100, Hiltjo Posthuma wrote:
> On Wed, Mar 27, 2024 at 04:11:27PM +0100, Storkman wrote:
> > On Sun, Feb 25, 2024 at 11:57:03AM +0100, g...@suckless.org wrote:
> > > commit 7473a8d1a57e5f9aba41b953f4e498c35e1c9dc5
> > > Author: Quentin Rameau
> > >
On Wed, Mar 27, 2024 at 04:11:27PM +0100, Storkman wrote:
> On Sun, Feb 25, 2024 at 11:57:03AM +0100, g...@suckless.org wrote:
> > commit 7473a8d1a57e5f9aba41b953f4e498c35e1c9dc5
> > Author: Quentin Rameau
> > AuthorDate: Sun Feb 25 01:31:31 2024 +0100
> > Commit: Hiltjo Posthuma
> >
On Sun, Feb 25, 2024 at 11:57:03AM +0100, g...@suckless.org wrote:
> commit 7473a8d1a57e5f9aba41b953f4e498c35e1c9dc5
> Author: Quentin Rameau
> AuthorDate: Sun Feb 25 01:31:31 2024 +0100
> Commit: Hiltjo Posthuma
> CommitDate: Sun Feb 25 11:56:43 2024 +0100
>
> Fix cursor move with
Hi,
As this is a topic more about sbase/ubase organization more
than about patches I am going to move the discussion to the
dev mailing list. Please, answer there instead of here in
hackers.
Regards,
Hi,
I was thinking about what to do with these patches adding new
commands. They raised a concern about what should be the scope of
sbase. The idea of sbase was to provide a minimal portable POSIX
base, while having ubase for the POSIX commands that cannot be
implemented in a portable way.
Hi,
On Thu, Mar 07, 2024 at 02:52:49PM -0500, neeshy wrote:
> On Thu Mar 7, 2024 at 1:19 PM EST, Roberto E. Vargas Caballero wrote:
> > I think it makes it simpler while keeping the correct behaviour that I
> > broke.
>
> Looks good to me!
Pushed!
On Thu Mar 7, 2024 at 1:19 PM EST, Roberto E. Vargas Caballero wrote:
> I think it makes it simpler while keeping the correct behaviour that I broke.
Looks good to me!
Hi,
On Thu, Mar 07, 2024 at 02:18:28AM -0500, neeshy wrote:
> It seems that the modifications you made break the use case where su is
> called without a username. It would normally default to the root
> user, but now it invokes usage() instead. My original patch worked as
> intended. Could you
On Wed Mar 6, 2024 at 4:14 AM EST, Roberto E. Vargas Caballero wrote:
> Hi,
>
>
> On Mon, Feb 12, 2024 at 04:25:49PM -0500, neeshy wrote:
> > Inline dologin, and simplify common code
>
> I have applied the 4 patches with a minor modification to the 1st
> one.
>
> Kind regards,
> Roberto Vargas.
Hi,
On Tue, Mar 05, 2024 at 09:20:57PM +0100, Elie Le Vaillant wrote:
> ---
> tar.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tar.c b/tar.c
> index 0361b63..405b8d9 100644
> --- a/tar.c
> +++ b/tar.c
> @@ -423,7 +423,7 @@ chktar(struct header *h)
>
Hi,
On Mon, Feb 12, 2024 at 04:25:49PM -0500, neeshy wrote:
> Inline dologin, and simplify common code
I have applied the 4 patches with a minor modification to the 1st
one.
Kind regards,
Roberto Vargas.
> - *state = ts.tv_nsec;
> + *state = (intptr_t) ^ time(NULL) ^ (ts.tv_nsec * 0xAC5533CD);
tv_nsec is `long` which is signed. Signed interger overflow is
undefined. You need to cast it to `unsigned long` before multiply:
... ^ ((unsigned long)ts.tv_nsec * 0xAC5533CD)
- NRK
On Mon, Mar 4, 2024 at 5:03 PM Elie Le Vaillant wrote:
>
> Thanks NRK
> ---
> libutil/random.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/libutil/random.c b/libutil/random.c
> index 780ba29..6b795a9 100644
> --- a/libutil/random.c
> +++ b/libutil/random.c
> @@
> + while (i < n && (c = fgetc(fp)) != EOF) {
> + if (fputc(c, stdout) == EOF)
I don't see this as an improvement. Each one of the fgetc and fputc are
going to go through a mutex lock (along with possibly going through a
call into a dynamic function).
I think the current solution
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
> +
Hi,
On Sun, Feb 11, 2024 at 09:26:14AM +0100, Elie Le Vaillant wrote:
> Some tar archives (eg. ftp://ftp.gnu.org/gnu/shtool/shtool-2.0.8.tar.gz)
> use leading spaces instead of leading zeroes for numeric fields.
> Although it is not allowed by the ustar specification, most tar
> implementations
On Tue, Mar 05, 2024 at 01:16:36PM +0100, Roberto E. Vargas Caballero wrote:
> Hi,
>
> On Sat, Feb 10, 2024 at 11:57:38PM +0100, Elie Le Vaillant wrote:
> > @@ -399,10 +400,17 @@ sanitize(struct header *h)
> > for (i = 0; i < LEN(fields); i++)
> > - for (j = 0; j < fields[i].l; j++)
Hi,
On Sat, Feb 10, 2024 at 11:57:38PM +0100, Elie Le Vaillant wrote:
> @@ -399,10 +400,17 @@ sanitize(struct header *h)
> for (i = 0; i < LEN(fields); i++)
> - for (j = 0; j < fields[i].l; j++)
> + for (leading = 1, j = 0; j < fields[i].l; j++)
>
Eric Pruitt wrote:
> I think there should be separate implementations for seekable vs
> non-seekable files to avoid buffering the entire contents of
> the file in memory unnecessarily.
In fact, performance could be also improved for non-seekable files
by forcing a seekable context, ie. use a
On Mon, Mar 04, 2024 at 10:24:36PM +0200, Tommi Hirvola wrote:
> On Mon, Mar 04, 2024 at 01:55:29PM +0100, Hiltjo Posthuma wrote:
> > I'm not sure about it. You could still chain REP sequences and "DoS" it.
>
> Fortunately, chained REP sequences can be terminated with ^C. You can
> try this by
On Mon, Mar 04, 2024 at 01:55:29PM +0100, Hiltjo Posthuma wrote:
> I'm not sure about it. You could still chain REP sequences and "DoS" it.
Fortunately, chained REP sequences can be terminated with ^C. You can
try this by copy-pasting the following line into st and pressing CTRL+C:
$ for i in
On Mon, Mar 04, 2024 at 12:56:30PM +0200, Tommi Hirvola wrote:
> Previously, printf 'L\033[2147483647b' would call tputc('L') 2^31 times,
> making st unresponsive. This commit allows repeating the last character
> at most 65535 times in order to prevent freezing and DoS attacks.
> ---
> st.c | 2
On Sun, Mar 03, 2024 at 03:05:47PM +0100, Eolien55 wrote:
> but should we not rather implement "Debiased Int Mult (t-opt)"?
Both should be fine. The integer mul method avoids clz() so that could
be a reason to prefer it.
> arc4random(3) doesn't uses seeds, which means that I cannot initialize
>
NRK wrote:
> I'd recommend using the bitmask approach described in here:
> https://www.pcg-random.org/posts/bounded-rands.html#bitmask-with-rejection-unbiased-apples-method
I thought the approach used by OpenBSD was simpler, and performed better,
becaused it avoided the loop, which might cause
On Sun, Mar 03, 2024 at 12:58:20AM +0100, Elie Le Vaillant wrote:
> I'm using the web interface to the mailing list to check what has been
> sent, and these patches were not sent.
The web archive is not reliable and often drops mails.
> + * Copied off OpenBSD (original is arc4random_uniform)
> +
"Roberto E. Vargas Caballero" wrote:
> I know that there are some pending patches for sbase and ubase,
> but I am a bit busy these days and I will not be able to look
> a bit deeper on them until next week. Be patient until then :)
>
> Thank you
Sure, no problem! I've sent most of the patches
On Sun Feb 25, 2024 at 8:13 AM CST, Quentin Rameau wrote:
> Would you have a suggestion about how to handle cursor absolute
> position with text position, maybe we need some addition state?
I would suggest that cursor position control sequences should always operate on
a single-column basis. This
> Hi,
Hola k0ga,
> > st would always move back 1 column,
> > even with wide glyhps (using more than a single column).
> >
> > The glyph rune is set on its first column,
> > and the other ones are to 0,
> > so loop until we detect the start of the previous glyph.
>
>
Hi,
On Sun, Feb 25, 2024 at 11:57:03AM +0100, g...@suckless.org wrote:
> st would always move back 1 column,
> even with wide glyhps (using more than a single column).
>
> The glyph rune is set on its first column,
> and the other ones are to 0,
> so loop until we detect
On Sun, Feb 18, 2024 at 06:56:49AM -0600, Tim Culverhouse wrote:
> The handler for 'S' final character does not check for a private
> marker. This can cause a conflict with a sequence called 'XTSMGRAPHICS'
> which also has an 'S' final character, but uses the private marker '?'.
> Without checking
Hi,
On Mon, Jan 22, 2024 at 02:18:10PM -0700, Randy Palamar wrote:
> As pointed out in a mail to dev expr was segfaulting when multiple
> math operations were specified on the command line: eg. 'expr 3 \*
> 2 + 1'. This happens because the tonum(), introduced in e50d533,
> assumed that v->str was
Hi,
On Sun, Jan 07, 2024 at 11:02:18AM -0700, Randy Palamar wrote:
> POSIX specifies that if the pattern contains a subexpression then
> the first matched subexpression should be returned if it exists.
>
> This fixes things like the following:
>
> ./expr 3 : '\(.*\)'
> Before: 3
> After:
Hi
On Sun, Jan 07, 2024 at 11:02:17AM -0700, Randy Palamar wrote:
> Comparison operations (>, <, =, etc.) and matching operations must
> operate originally provided string not one that has gone back and
> forth through string formatting. This caused operations such as
> the following to give
Hi,
On Sun, Dec 24, 2023 at 12:07:44PM +0100, Rene Kita wrote:
> On Wed, Dec 13, 2023 at 12:55:26PM +0100, Roberto E. Vargas Caballero wrote:
> > It changes to read full lines before executing commands, escaping
> > newlines when it is needed. It solves 2 different cases:
> >
> > -
Hi,
On Tue, Dec 26, 2023 at 03:40:36PM +0100, Страхиња Радић wrote:
> On 23/12/24 11:46AM, Rene Kita wrote:
> > > + if (!from) {
> > > + len = 0;
> > > + t = NULL;
> > > + } else {
>
> This seems redundant. Normally, NULL shouldn't be passed, and even if it is,
> it
> is the
Hi,
On Sun, Dec 24, 2023 at 11:46:26AM +0100, Rene Kita wrote:
> Nit as it's more a matter of style: I'd prefer to have one function to
> create a String and another function to create a String from a char
> array. This would make a cleaner interface and avoids passing and
> dealing with NULL all
On 23/12/24 11:46AM, Rene Kita wrote:
> > + if (!from) {
> > + len = 0;
> > + t = NULL;
> > + } else {
This seems redundant. Normally, NULL shouldn't be passed, and even if it is, it
is the responsibility of the "user-programmer" (think libc functions). This is
further
On Wed, Dec 13, 2023 at 12:55:26PM +0100, Roberto E. Vargas Caballero wrote:
> It changes to read full lines before executing commands, escaping
> newlines when it is needed. It solves 2 different cases:
>
> - Substitution commands with newlines in the replace part
This does not work with
Comment inline.
On Wed, Dec 13, 2023 at 12:55:27PM +0100, Roberto E. Vargas Caballero wrote:
> This makes possible to use the function to initialize the string from
> an existing char array.
> ---
> ed.c | 30 +-
> 1 file changed, 21 insertions(+), 9 deletions(-)
>
>
good, thank you. (:
On Wed, 13 Dec 2023 19:12:00 +0100
Hiltjo Posthuma wrote:
> Hi,
>
> Thanks, I've applied the patch and fixed a tiny typo in the debug message.
>
> I haven't tested the patch, but I trust you that it works.
>
> Of course if people notice bugs, feel free to report them.
>
Hi,
Thanks, I've applied the patch and fixed a tiny typo in the debug message.
I haven't tested the patch, but I trust you that it works.
Of course if people notice bugs, feel free to report them.
On Wed, Dec 13, 2023 at 04:30:17PM +0400, նորայր wrote:
> also no need to know armenian to test.
also no need to know armenian to test.
just run ./svkbd-mobile-intl and type lowercase and uppercase in armenian
layout.
do that for the patched version and you'll see the difference.
for some reason on sxmo/postmarketos i have to restart the device in order to
run a newer binary. though i
ok let me try to explain this very simply.
some time ago i have added armenian and dvorak layouts.
i have noticed that in dvorak and all other layouts uppercase characters work.
while you don't have to do any extra effort for that. let's say:
```
{ 0, 0, XK_a, 1 },
{ 0, 0, XK_o, 1
Hi,
On Fri, Dec 01, 2023 at 01:33:36PM +0100, Jules Maselbas wrote:
> when sbase-box is executed without argument, the check sbase-box
> options doesn't verify the argument count leading to a segfault.
>
> Add a check on the argc before parsing sbase-box options (currently
> only `-i`)
Applied,
Hi,
On Wed, Nov 15, 2023 at 08:56:56AM +0100, Rene Kita wrote:
> > I think the way to fix this problem is reading the full command before
> > executing it, otherwise there are so many traps. I am going to try to
> > fix this in th enext days.
>
> I had the same idea. Reading the full command
On Sun, Dec 03, 2023 at 08:22:04PM +0400, norayr chilingarian wrote:
> ---
> svkbd.c | 11 ++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/svkbd.c b/svkbd.c
> index e4dbd15..cce2463 100644
> --- a/svkbd.c
> +++ b/svkbd.c
> @@ -481,9 +481,18 @@ press(Key *k, KeySym
On Tue, Nov 14, 2023 at 07:42:03PM +0100, Roberto E. Vargas Caballero wrote:
> Hi,
>
> On Sun, Nov 05, 2023 at 02:38:20PM +0100, Rene Kita wrote:
> > On Fri, Nov 03, 2023 at 01:32:37PM +0100, Rene Kita wrote:
> > > borked patch
> >
> > Patch is not sufficient, sorry for the noise.
>
[...]
> I
Hi,
On Sun, Nov 05, 2023 at 02:38:20PM +0100, Rene Kita wrote:
> On Fri, Nov 03, 2023 at 01:32:37PM +0100, Rene Kita wrote:
> > borked patch
>
> Patch is not sufficient, sorry for the noise.
I have this problem in my radar. I began to write a solution for it,
but I had to switch to implement
Applied, thanks.
Applied, thanks.
Applied, thanks.
Applied, thanks.
Applied, thanks.
Applied, thanks.
On Fri, Nov 03, 2023 at 01:32:37PM +0100, Rene Kita wrote:
> borked patch
Patch is not sufficient, sorry for the noise.
> > I guess that the original intent of the code here
> > was to to find any executable file.
>
> I concur. It seems to me that the default output mode for `cc` is 755
> even if the parent directory has more restrictive permissions. So the
> more concise -perm -111 should suffice. I will leave
> Not exactly, -perm -111 matches if at least the mode has executable bit
> for all (could be 751 for example),
> while GNU -perm /111 matches if any bit is set (could be 500).
Thanks for the info, I didn't really check the GNU manpage.
> I guess that the original intent of the code here
> was
> Hi Quentin,
Hola Randy,
> > -find . ! -name . -prune -type f -perm /111 |
> > +find . ! -name . -prune -type f \( -perm -u+x -o -perm -g+x -o -perm o+x
> > \) |
>
> I believe `-perm -111` is equivalent and specified by POSIX.
Not exactly, -perm -111 matches if at least the mode has
Hi Quentin,
> -find . ! -name . -prune -type f -perm /111 |
> +find . ! -name . -prune -type f \( -perm -u+x -o -perm -g+x -o -perm o+x \) |
I believe `-perm -111` is equivalent and specified by POSIX.
- Randy
On Thu, Oct 12, 2023 at 12:40:15PM +0200, Peter Hofmann wrote:
> It has been brought to my attention that this patch breaks pasting text
> in older versions of Vim, e.g. the ones coming with OpenBSD 7.2 or
> Ubuntu 22.04. The ncurses terminfo db mentions that Vim 9.0.1117 or
> newer is needed.
>
It has been brought to my attention that this patch breaks pasting text
in older versions of Vim, e.g. the ones coming with OpenBSD 7.2 or
Ubuntu 22.04. The ncurses terminfo db mentions that Vim 9.0.1117 or
newer is needed.
IIUC, old Vim doesn't read PS/PE from terminfo but it does read BE/BD,
so
Hi Hiltjo,
you're welcome, and thanks for merging.
Cheers
Peter
On Sat, Oct 07, 2023 at 07:40:45AM +0200, Peter Hofmann wrote:
> From: Peter Hofmann
>
> It is unclear if it's "required" to do this on RIS, but it's useful when
> calling reset(1) after interactive programs have crashed and garbled up
> the screen.
>
> FWIW, other terminals do it as well
On 230924-093006, Hiltjo Posthuma 'hil...@codemadness.org' wrote:
>
>
>On Sun, Sep 24, 2023 at 05:34:48AM +, suiso67@macadamia.rocks wrote:
>> From: suiso67
>>
>> ---
>> config.def.h | 43 +++
>> dwm.c| 47
Applied.
On Fri, 2023-09-22 at 15:12 +0200, Hiltjo Posthuma wrote:
> On Sun, Sep 17, 2023 at 12:11:28AM +, Tom Schwindl wrote:
> > ---
> > Makefile | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Makefile b/Makefile
> > index 470ac86407bb..6eb2d9d04852 100644
> > ---
On Sun, Sep 24, 2023 at 05:34:48AM +, suiso67@macadamia.rocks wrote:
> From: suiso67
>
> ---
> config.def.h | 43 +++
> dwm.c| 47 +++
> 2 files changed, 90 insertions(+)
>
> diff --git
On Sun, Sep 17, 2023 at 12:11:28AM +, Tom Schwindl wrote:
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index 470ac86407bb..6eb2d9d04852 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -40,7 +40,7 @@ dist: clean
> tar -cf
Hi,
On Sun, Jul 30, 2023 at 10:15:49AM +0300, sewn wrote:
> From 9f4be567ff25fee986976c6afa193223496013a6 Mon Sep 17 00:00:00 2001
> From: sewn
> Date: Fri, 28 Jul 2023 18:58:37 +0300
> Subject: [PATCH] xargs: add replace string flag (-I)
I have applied the patch with some small modifications
On Sun, Aug 06, 2023 at 03:03:21PM +0200, Markus Rudy wrote:
> This header used to be included by sys/types.h in glibc, and musl
> adopted the behaviour. However, this dependency was never desired, so
> glibc deprecated it in 2016 and finally removed it in 2019, and so
Applied.
Hi,
On Sun, Aug 06, 2023 at 10:50:25PM +0200, noneofyourbusin...@danwin1210.de
wrote:
> a simple test case:
>
> printf ab3 | tr -c '[:alpha:]' '\n'
Applied.
Open source writes:
Some people like me find it beautiful, simple, and comfortable eye,
It's a personal preference at the end of the day, it's just a simple
patch for those who want it.
This mailing list is for mainline patch submissions and discussion, please
submit other things to the
On 9/1/23 23:16, Ethan Marshall wrote:
I do not like this color scheme, the old iconic suckless blue is much
better! Why does it need changing?
Some people like me find it beautiful, simple, and comfortable eye, It's
a personal preference at the end of the day, it's just a simple patch
for
> I do not like this color scheme, the old iconic suckless blue is much
> better! Why does it need changing?
It is possible that this was intended to be submitted to the wiki
instead. In which case, http://suckless.org/hacking/.
Ethan
On Fri, Sep 01, 2023 at 08:44:50PM +0300, anas.elgarhy@gmail.com wrote:
> From: Anas Elgarhy
>
> ---
> config.def.h | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/config.def.h b/config.def.h
> index 9efa774..d357f2c 100644
> --- a/config.def.h
> +++
On Wed, Aug 30, 2023 at 11:25:18AM -0700, Jeremy wrote:
> On 08/30/23 05:41PM, Christopher Lang wrote:
> > This would be my implementation for executing all selected commands:
> >
> > #!/bin/sh
> > for x in $(dmenu_path | dmenu "$@"); do
> > echo "$x" | ${SHELL:-"/bin/sh"} &
> > done
> >
> > I
On Wed, Aug 30, 2023 at 05:41:28PM +0100, Christopher Lang wrote:
> On Wed, Aug 30, 2023 at 05:48:13PM +0200, Страхиња Радић wrote:
> > On 23/08/30 09:43AM, Randy Palamar wrote:
> > > Personally I see little need for such a patch. I don't really
> > > think anyone is pressing + by mistake; they
>
On 08/30/23 05:41PM, Christopher Lang wrote:
> This would be my implementation for executing all selected commands:
>
> #!/bin/sh
> for x in $(dmenu_path | dmenu "$@"); do
> echo "$x" | ${SHELL:-"/bin/sh"} &
> done
>
> I suppose this behaviour is more intuitive, but it is a little more
>
On Wed, Aug 30, 2023 at 05:48:13PM +0200, Страхиња Радић wrote:
> On 23/08/30 09:43AM, Randy Palamar wrote:
> > Personally I see little need for such a patch. I don't really
> > think anyone is pressing + by mistake; they
> > are nowhere near each other on most (all?) keyboard layouts.
A dmenu
On 23/08/30 09:43AM, Randy Palamar wrote:
> Personally I see little need for such a patch. I don't really
> think anyone is pressing + by mistake; they
> are nowhere near each other on most (all?) keyboard layouts.
>
> Actually I didn't even know about this feature despite using
> dmenu in a
On Wed, Aug 30, 2023 at 6:13 AM Christopher Lang
wrote:
>
> Using +, multiple selections can be make in dmenu, each
> outputting on a new line. If multiple selections are made in dmenu_run
> then multiple lines will be piped to $SHELL which will not be properly
> handled.
>
> This patch only
On Sun, Aug 27, 2023 at 08:09:47PM +0100, Christopher Lang wrote:
> To get more feedback on this patch, I will submit it to the wiki under
> the name fixmultimon. In the patch wiki page, I will add a message
> explaining it is intended for the mainline but is waiting for more
> feedback.
>
> --
>
To get more feedback on this patch, I will submit it to the wiki under
the name fixmultimon. In the patch wiki page, I will add a message
explaining it is intended for the mainline but is waiting for more
feedback.
--
Christopher
On 23/08/17 09:22, Christopher Lang wrote:
> Say you have two tiled monitors: M1 and M2. M1 and M2 each contain a
> single client occupying their full area. M1 is selected, the pointer is
> in M2. If a keybinding is pressed that moves M1's client to M2, then the
> new monitor selected depends on
On Wed, Aug 16, 2023 at 07:30:05PM +0200, Hiltjo Posthuma wrote:
> On Wed, Aug 16, 2023 at 06:06:40PM +0200, Storkman wrote:
> > On Wed, Aug 16, 2023 at 10:07:16AM +0200, Hiltjo Posthuma wrote:
> > > On Tue, Aug 15, 2023 at 10:43:32AM +0100, Christopher Lang wrote:
> > > > When the pointer is on
On Wed, Aug 16, 2023 at 06:06:40PM +0200, Storkman wrote:
> On Wed, Aug 16, 2023 at 10:07:16AM +0200, Hiltjo Posthuma wrote:
> > On Tue, Aug 15, 2023 at 10:43:32AM +0100, Christopher Lang wrote:
> > > When the pointer is on an unselected monitor and is not moving, it
> > > should not interfere
On Wed, Aug 16, 2023 at 10:07:16AM +0200, Hiltjo Posthuma wrote:
> On Tue, Aug 15, 2023 at 10:43:32AM +0100, Christopher Lang wrote:
> > When the pointer is on an unselected monitor and is not moving, it
> > should not interfere what window is selected/focused.
> > [...]
> > If focusmon selects a
On Tue, Aug 15, 2023 at 10:43:32AM +0100, Christopher Lang wrote:
> When the pointer is on an unselected monitor and is not moving, it
> should not interfere what window is selected/focused.
>
> 1:
>
> From
> https://tronche.com/gui/x/xlib/events/input-focus/normal-and-grabbed.html:
> When the
Perhaps his kidnappers have forced him to write this email 樂.
On Thu, Aug 3, 2023 at 3:20 PM Dr. André Desgualdo Pereira
wrote:
>
> That's a huge relief!
>
> On 03/08/2023 12:29, Christopher Lang wrote:
> > I was trying to subscribe to the mailing list but didn't get a response
> > from so I
That's a huge relief!
On 03/08/2023 12:29, Christopher Lang wrote:
> I was trying to subscribe to the mailing list but didn't get a response
> from so I tried this. I think I have figured it
> out not though.
> Sorry if I pinged you. And I'm fine haha.
> PS. I'm sorry if this is html mail, still
On Thu, 3 Aug 2023 12:29:04 +0100
Christopher Lang wrote:
Dear Christopher,
> I was trying to subscribe to the mailing list but didn't get a
> response from so I tried this. I think I
> have figured it out not though.
> Sorry if I pinged you. And I'm fine haha.
> PS. I'm sorry if this is html
I was trying to subscribe to the mailing list but didn't get a response
from so I tried this. I think I have figured it
out not though.
Sorry if I pinged you. And I'm fine haha.
PS. I'm sorry if this is html mail, still trying to set up a better email
client.
On Thu, 3 Aug 2023 at 12:14, Dr.
Can anyone track where Christopher is? Does anyone know a friend of him? Maybe
he was kidnapped or in risk of suicide. Maybe call local police?
On 02/08/2023 23:10, Christopher Lang wrote:
> help
On 23/07/12 10:28PM, Hiltjo Posthuma wrote:
> Unless I'm missing something. It seems like an application or environment
> issue.
>
> For dwm it is assumed the environment is utf-8 and application should use it.
Sorry, I forgot to list my locale-related variables. They are set up as such:
On Wed, Jul 12, 2023 at 06:48:45PM +0200, Страхиња Радић wrote:
> Hi, recently André Desgualdo Pereira reported a bug in dwm when window names
> consist only of characters in ISO 8859-1. In short, windows with such names
> had their names broken at the place of ISO 8859-1-specific characters
Hi Hiltjo,
On Thu, Jul 06, 2023 at 07:08:57PM +0200, Hiltjo Posthuma wrote:
> What hash algorithm is this exactly, it looks interesting? I've found it at:
>
> https://github.com/skeeto/hash-prospector
>
> Is that the one?
The "xor-shift multiply" construct itself is fairly popular and can
1 - 100 of 2780 matches
Mail list logo
