At work I have switched from XEmacs to GNU Emacs for various reasons. I
use ediff a LOT. With XEmacs, the ediff popup gets the focus but not so
with GNU Emacs. The focus always stays in the bottom right window. So I
end up with a lot on n characters in that windows (ediff users will
understand).
It would really help the world... ok, me... if the script was given the
reason it was being called. Mainly I want to know if it is a renewal.
diff --git a/sdhcp.c b/sdhcp.c
index e2a641e..b6cbfe7 100644
--- a/sdhcp.c
+++ b/sdhcp.c
@@ -322,7 +339,7 @@ dhcprecv(void)
}
static void
On Wed, 14 Nov 2018 17:13:15 -0800
Michael Forney wrote:
> On 2018-11-12, Sean MacLennan wrote:
> > I am surprised you are getting away with binding the socket to the
> > broadcast address.
>
> I found in ip(7):
>
> INADDR_BROADCAST (255.255.255.255) mean
So I instrumented dwm with some debugs and found that the terminal was
indeed grabbing focus with an enter notify.
So I found a workaround within GNU Emacs. Non GNU Emacs users can just
look away now.
(setf (alist-get 'top ediff-control-frame-parameters) 1)
(setf (alist-get 'left
On Mon, 8 Oct 2018 13:27:23 -0700
AR Garbe wrote:
> Hi Sean,
>
> try forcing that window as floating window via:
>
> { "Ediff", NULL, NULL, 0,1,
> -1 },
>
> or
>
> { "Emacs", "Ediff", NULL, 0,1,
> -1 },
>
> in the rules[] section of
On Sat, 5 Jan 2019 17:09:32 -0200
Caio Barros wrote:
> Although I too have a somewhat nostalgic
> feeling when typing a command to load the window manager, I don't mind
> at all automating it, but for that a DM is not necessary.
I almost always run X11... so I want it to startup when I login.
On Sat, 5 Jan 2019 15:12:41 -0600
Samuel Holland wrote:
> For a single-user laptop or workstation, why does there even need to
> be a concept of "logging in"? And why do you need 3-4 layers of
> shells running in the background to manage your X session? You've got:
> - your login shell
> -
On Tue, 25 Dec 2018 08:16:47 -0600
Cág wrote:
> I'm thinking of something you can compile the Linux kernel[0] with.
The Linux kernel only compiles with the GNU toolchain. There are
efforts to get it compiling with clang but I believe they are not there
yet.
The Linux kernel is portability
On Tue, 25 Dec 2018 12:31:50 -0600
Cág wrote:
> Wrong. Not even you can compile it with Clang, (HOSTCC=clang
> CC=clang), but link it with lld:
> http://lists.llvm.org/pipermail/llvm-dev/2017-January/109288.html
Sorry, I should have said you can't compile a *working* kernel with
clang. They are
An update. There is a bug in the raw socket code I posted. It does not
try hard enough to make sure that the packet is for us. So it can,
and will, end up thinking a different ack is ours. I found this trying
to connect to Rogers.
If you go to the github (https://github.com/smaclennan/sdhcp) and
I have attached a more complete diff. This diff has Linux raw sockets,
portability, and some bug fixes. I have also pushed the changes to
github and they can be found here: https://github.com/smaclennan/sdhcp.
The diff is quite big, but not really that complicated. The main change
is moving all
On Sat, 2 Feb 2019 22:28:33 -0800
Michael Forney wrote:
> On 2019-02-02, Sean MacLennan wrote:
> > First a question: how portable do we want things? The current sdhcp
> > works only on Linux.
>
> I think that depends on how feasible it is to make it portable without
On Sat, 2 Feb 2019 18:15:26 +
sylvain.bertr...@gmail.com wrote:
> Hi,
>
> I am looking at xml parsers.
>
> I am about to go expat, but I am wondering if there are some
> interesting alternatives I did miss?
>
Json? Not sure what you need the xml parser for... but does it have to
be xml?
Not sure if I this list allows attachments... so here we go.
First a question: how portable do we want things? The current sdhcp
works only on Linux.
This patch contains one big change and some smaller changes. The big
change is support for raw sockets on Linux. I split the raw socket code
into
I would say give it a try. After using the same window manager for a
long time, I switched to dwm. I tried just about every window manager
(ok, probably not true since there are so many obscure ones) but always
went back to my favourite. dwm was the only one that stuck and was a
big change for me.
I found a couple of bugs in sdhcp... both having to do with
renewal. If you are having problems renewing your lease or find that
your IP keeps changing... read on.
The first problem is that sdhcp assumes the renew and rebind times
will be set. These fields are optional, only the lease time is
On Wed, 7 Jul 2021 08:55:07 +0800
Patrick <201009-suckl...@planhack.com> wrote:
> Hi all,
>
> What's a good minimal sshd?
>
> Or should we just run stunnel + telnetd?
>
>
> Patrick
>
>
dropbear
https://matt.ucc.asn.au/dropbear/dropbear.html
Cheers,
Sean
On Fri, 11 Feb 2022 11:47:56 +
Daniel Littlewood wrote:
> I wonder whether there are any text-editing (particularly
> code-editing) workflows people have had success with which combine
> many small programs, rather than using a single monolith.
On development machines there are two places
On Sun, 22 Oct 2023 11:12:09 +0200
Arthur Jacquin wrote:
> Undo-ing is clearly a non-trivial feature.
I wrote my own editor (zedit or z) in the late '80s. At that time none
of the editors I was using had undo... so I didn't add it.
It wasn't until I switched to emacs a decade later that I had
On Thu, 05 Oct 2023 16:25:25 +0200
Josuah Demangeon wrote:
> Which would provide something acting like Ethernet,
> but out of a serial cable instead of a cat6 cable.
They could be running serial over a cat6 cable. Some of the embedded
systems I am using do this. There is no ethernet involved,
On Tue, 24 Oct 2023 01:26:24 +0200
Arthur Jacquin wrote:
> I'm interested in having a look at the code too, in case you want to
> share it ;)
No problem. See the README.md for a brief history of zedit. It is
probably too big to be suckless, even in its greatly reduced state.
Most of the cool
I started writing ipaddr almost 20 years ago after the umpteenth
time trying to parse ifconfig (and later ip) output in scripts. The
original version was get only and Linux only.
It now supports Linux, QNX, and most BSDs. However, I rarely use BSD
these days... so the set functions may not work
On Sun, 26 Mar 2023 10:54:19 -0700
Jeremy wrote:
> One alternative is to just get the address from ifaddrs->ifa_addr.
That is what I did.
# /tmp/ipaddr
192.168.1.115 (genet0)
192.168.2.2 (genet0)
However, I am not sure what to do if you ask for the ip of the
interface:
# /tmp/ipaddr genet0
On Mon, 1 May 2023 09:45:22 -0700
Jeremy wrote:
> Pretty neat that you don't use NAT. I had a public IP on my laptop
> once(ONCE) & the Chinese kept sending garbage to any port that was
> open & it made my laptop hot(almost burned my thighs!) What's your
> secret to avoid this??
I had a public
On Mon, 27 Mar 2023 14:32:39 -0400
fo...@dnmx.org wrote:
> Sorry because I don't really care about the project other than "more
> suckless = better", but I got a question: why GitHub?
> It's literally depending on Microsoft.. we all know how companies
> like MS and Google like to change shit all
25 matches
Mail list logo
