On 03/09/2021, Marc Chantreux wrote:
>> 'abc' in FILE, from within vi.
>
> * % means 'the current file' in vi commands so you can write
That's helpful; thank you!
> * | is the command separator
> * grep has a -c flag to count occurrences
>
> so you can write:
>
> :w|grep -c abc %
That doesn
>
> It looks like it is probably a Qualcomm-based device. It seems likely
>
> that as things are now, it will attach to umsm. I can't say for sure if
>
> it will work or not though I think there is a fairly good chance.
>
> But unless you are lucky and somebody already used the same device,
>
>
On 2021-09-03, Donovan Watteau wrote:
> (As for "the problem I'm trying to solve": ERL has no clock, ntpd -s is
> gone, but ntpd relies on DNS, and Unbound enables DNSSEC, so this system
> is indefinetly stuck between unbound and ntpd errors if I reboot and if
> the kernel infers a date that's too
On 9/3/21 12:35 PM, Jeff Ross wrote:
On 9/3/21 3:45 AM, Stuart Henderson wrote:
On 2021-09-02, Jeff Ross wrote:
This is a multi-part message in MIME format.
--F51C046C214039690CD908CB
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Hi all,
> 'abc' in FILE, from within vi.
* % means 'the current file' in vi commands so you can write
* | is the command separator
* grep has a -c flag to count occurrences
so you can write:
:w|grep -c abc %
you can also write the content of the buffer to a pipe (my prefered
solution here):
:w
Hi,
Amd64 page (https://ftp.openbsd.org/amd64.html) states that:
The only major shortcoming at this time is that the kernel
debugger ddb is somewhat poor.
Myself not being familiar with it, can someone explain to me why amd64
is considered "poor" and what shortcomings it has, relative to other
p
Hello,
On systems without an internal clock, I'm trying to understand how
OpenBSD makes a rough time estimation from the previous file system
state, immediately after a reboot.
It seems to be related to inittodr(9) in kern_time.c (seems to be MI in
6.9; earlier octeon releases would say "No TOD c
> i['d] forgotten & (not that useful in vim) but yes! now you reminds me, it
makes perfect sense to use it in nvi.
Speaking of things that make no sense in one vi clone but work in
another, I recently ended up looking for a way to count occurrences of
'abc' in FILE, from within vi.
In vim you just
On 9/3/21 3:45 AM, Stuart Henderson wrote:
On 2021-09-02, Jeff Ross wrote:
This is a multi-part message in MIME format.
--F51C046C214039690CD908CB
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Hi all,
I bought one of these mini computers
h
On 9/3/21 2:34 AM, Maurice McCarthy wrote:
At the boot prompt try
boot> boot hd1a:/bsd
If it works you can put it in boot.conf
HTH
Unfortunately, the boot process never gets to the boot prompt--it skips
right over the newly installed hard drive.
Jeff
hello,
> The bang command has an equivalent in vi.
this is the same command indeed but the ergonomy is quite different:
vi don't "generate" the begining of a command including the range so
we can't just delete a char and edit.
> The closest you
> can get to executing the same replacement via a v
>even if it's short, I really would like to have
>something which work the way I abuse the ! command in vim:
The bang command has an equivalent in vi.
>so I just have to replace the ! by s/foo/bar and i get the job done.
So far there is no vi command to perform such operation; bang is both a
v
hello people,
Does anyone know how to get this done even faster:
ma
}
:'a,ms/foo/bar
even if it's short, I really would like to have
something which work the way I abuse the ! command in vim:
!}
actually write a range on command line like
:.,.6!
so I just have to replace
On 2021-09-02, Jeff Ross wrote:
> This is a multi-part message in MIME format.
> --F51C046C214039690CD908CB
> Content-Type: text/plain; charset=utf-8; format=flowed
> Content-Transfer-Encoding: 8bit
>
> Hi all,
>
> I bought one of these mini computers
>
> https://www.amazon.com/dp/B084
At the boot prompt try
boot> boot hd1a:/bsd
If it works you can put it in boot.conf
HTH
15 matches
Mail list logo
