Marc Baudoin écrit :
> Greg Troxel écrit :
> >
> > When you upgrade packages, make sure you have every single package from
> > a consistent build - same branch, same OS version.
>
[...]
>
> In the case of QEMU, I don't see any direct dependency which
> could influence networking but I might be
On Fri, Jan 05, 2024 at 10:30:51AM -0600, Robert Nestor wrote:
> Maybe it?s just me, but putting an announcement of the availability
> of a Release Candidate at the top of the NetBSD Home Page without
> having a link to where it can be found seems highly inconvenient.
Not "without", but slightly h
Maybe it’s just me, but putting an announcement of the availability of a
Release Candidate at the top of the NetBSD Home Page without having a link to
where it can be found seems highly inconvenient. Having to dig thru three or
four links and pages to find it doesn’t seem to be helpful in encou
On Fri, 5 Jan 2024, Rhialto wrote:
The thing is that I used the lower case names (instance names instead of
class names) in the .Xresources on purpose. The reason was, if I
remember correctly, to make them work for both xterm and uxterm.
A change like this should work for that use-case, I thi
On Fri 05 Jan 2024 at 08:23:33 +, RVP wrote:
> On Thu, 4 Jan 2024, Rhialto wrote:
>
> > I do have in my ~/.Xresources:
> >
> > xterm.vt100.faceName: Lucida Console Semi-Condensed
> > xterm.vt100.faceSize: 9
> > XTerm.vt100.renderFont: false
> > UXTerm.vt100
On Thu, 4 Jan 2024, Rhialto wrote:
I do have in my ~/.Xresources:
xterm.vt100.faceName: Lucida Console Semi-Condensed
xterm.vt100.faceSize: 9
XTerm.vt100.renderFont: false
UXTerm.vt100.renderFont:true
You've put the instance-names (lower-case initial char.