On Wed, Jan 04, 2023 at 10:12:00AM +, Stuart Henderson wrote:
>I don't think this helps.
>It's the same for clean, update-patches, install, update-plist,
>port-lib-depends-check, [...] and we already have "and of course, use
>the same settings for the subsequent invocations of
Hi Crystal,
I tried your patch on my laptop. With it applied, and my TERM set to
'xterm', I do get colors in mutt and tmux. The latter, however, shows
'^@^@' before the PS1 prompt upon starting a new session (`tmux new`),
behavior I don't see with a 'real' xterm.
I like the idea, thanks for
On Wed, Jan 04, 2023 at 04:42:55PM +0100, Paul de Weerd wrote:
> Hi Crystal,
>
> I tried your patch on my laptop. With it applied, and my TERM set to
> 'xterm', I do get colors in mutt and tmux.
Great! Thanks for testing :).
> The latter, however, shows
> '^@^@' before the PS1 prompt upon
On Wed, Jan 04, 2023 at 08:08:48PM +0100, Paul de Weerd wrote:
> On Wed, Jan 04, 2023 at 02:33:57PM -0300, Crystal Kolipe wrote:
> | On Wed, Jan 04, 2023 at 04:42:55PM +0100, Paul de Weerd wrote:
> | > Hi Crystal,
> | >
> | > I tried your patch on my laptop. With it applied, and my TERM set to
>
Hi all,
This patch removes a few remnants of the unsupported diff -l
option from diff.c and the diff manual page.
The diff.c usage() print is already correct, so no changes are
needed there.
Thanks,
Nate
diff --git a/usr.bin/diff/diff.1 b/usr.bin/diff/diff.1
index 85a168d7740..e718e37ed61
On Wed, Jan 04, 2023 at 02:33:57PM -0300, Crystal Kolipe wrote:
| On Wed, Jan 04, 2023 at 04:42:55PM +0100, Paul de Weerd wrote:
| > Hi Crystal,
| >
| > I tried your patch on my laptop. With it applied, and my TERM set to
| > 'xterm', I do get colors in mutt and tmux.
|
| Great! Thanks for
Dear Sergii and others,
I've committed the change that passes the ESRT from the bootloader to
the kernel. So now it is time to add the interfaces to the kernel to
read it. And add the interfaces to manipulate EFI variables.
For those out of the loop: this could allow us to run fwupd on
On Wed, 04 Jan 2023 13:13:28 -0800, Nathan Houghton wrote:
> This patch removes a few remnants of the unsupported diff -l
> option from diff.c and the diff manual page.
>
> The diff.c usage() print is already correct, so no changes are
> needed there.
Thanks, committed.
- todd
Now that we have resolved the problems with the UltraSPARC IIe, let's
try the clockintr switch again. For reference, here is v1:
https://marc.info/?l=openbsd-tech=166776418803680=2
The major difference in v2 is that we send_softint() if we miss when
setting the comparison register instead of
Continuing the move towards xterm becoming the default termtype for the
console...
This third version of the patchset adds the following features. New features
since the last version are highlighted first:
NEW - Control sequences for dim text, invisible text, strike through, italic,
and
Hello,
There was recently a bug report opened for the ansible module
openbsd_pkg, where someone was getting errors due to pkg_add disliking
their TERM setting:
https://github.com/ansible-collections/community.general/issues/5738
Basically they are running TERM=xterm-kitty locally, which makes
Jose Maldonado writes:
> Right now I'm using OBSD 7.2 (my first time in OBSD) and the only issue
> is my onboard audio. The audio randomly stuck (listen music or not, with
> high CPU use or not) and only a hard reboot give me back audio to next
> stuck.
>
> In dmesg don´t show nothing, but
Le 04/01/2023 14:22, Stuart Henderson a écrit :
On 2023-01-04, Nick Holland wrote:
On 1/4/23 01:13, Sylvain Saboua wrote:
Hi, my openbsed (encrypted) install is functionning really
well, apart from one thing, that would signal a bug or smth:
The initial boot process, right after I type the
Hello,
I agree with change as-is. Though I have some suggestions
for few finishing touches. see comments inline.
On Wed, Jan 04, 2023 at 01:15:54PM +1000, David Gwynne wrote:
> move the pf_state_tree_id type from pfvar.h to pfvar_priv.h.
>
> this is like the pf_state_tree change from yesterday.
> On 4 Jan 2023, at 20:20, Alexandr Nedvedicky wrote:
>
> Hello,
>
> I agree with change as-is. Though I have some suggestions
> for few finishing touches. see comments inline.
>
> On Wed, Jan 04, 2023 at 01:15:54PM +1000, David Gwynne wrote:
>> move the pf_state_tree_id type from pfvar.h
bgpd already supports Open Policy (RFC 9234) and the role of the router is
set as part of the `announce policy` config. Now ASPA also needs the role
so it makes sense to promote setting the role in the config.
I also switched the role to an enum mainly because I want 0 to be the
default "NONE"
I don't think this helps.
It's the same for clean, update-patches, install, update-plist,
port-lib-depends-check, [...] and we already have "and of course, use the
same settings for the subsequent invocations of make" in the section
showing how to work with flavours.
--
Sent from a phone,
and "stp" for pf_state ** variables.
there should be no functional change here.
ok?
Index: pf.c
===
RCS file: /cvs/src/sys/net/pf.c,v
retrieving revision 1.1167
diff -u -p -r1.1167 pf.c
--- pf.c4 Jan 2023 10:31:55 -
On Wed, Jan 04, 2023 at 12:21:59PM +0100, Claudio Jeker wrote:
> bgpd already supports Open Policy (RFC 9234) and the role of the router is
> set as part of the `announce policy` config. Now ASPA also needs the role
> so it makes sense to promote setting the role in the config.
>
> I also
19 matches
Mail list logo
