Historically 's' presumably stood both for step and seed, but since we
don't support seed anymore I think it's wise to make things a little
more readable and just rename 's' to 'step'.
tb@ already agrees with the concept.
OK?
martijn@
Index: jot.1
===
Looking at tb's diff I fell in the trap of looking at other parts of the
code. Now he's conning me into writing diffs...
So here's the first one:
- When -b is set, but followed by -w it doesn't remove the boring flag
and the -w is interpreted as a -b string
- -c is defined as "This is an abbrevi
If jot is run without arguments, prec will never be changed from -1.
This results in the nonsensical format string "%.-1f" being produced in
getformat(). __vfprintf() will misinterpret the - as a left adjustment
flag and the precision used will be 0. The result is the samw as "%.0f",
which is what
It would be nice if someone running i386 could apply this diff, run
without apmd and check that setting sysctl hw.setperf to different
values between 0 and 100 works and changes hw.cpuspeed as expected.
hw.cpuspeed should take on the all the values reported in dmesg, e.g.,
cpu0: Enhanced SpeedStep
Hi,
The ure_stop_task is not scheduled anywhere. In fact, it has never been
used. Remove it.
So long,
- Christian
---
sys/dev/usb/if_ure.c| 3 ---
sys/dev/usb/if_urereg.h | 1 -
2 files changed, 4 deletions(-)
diff --git a/sys/dev/usb/if_ure.c b/sys/dev/usb/if_ure.c
index ea73db00954..0
Ingo Schwarze:
> deraadt@ recently pointed out to me in private mail that it is good
> for usability if interactive programs providing line editing
> functionality are consistent what they do with Ctrl-C, ideally
> discard the current input line and provide a fresh prompt.
>
> So i propose to do
Hi Martijn,
Martijn van Duren wrote on Thu, Aug 12, 2021 at 04:37:24PM +0200:
> Maybe I've used cdio once or twice and I don't have a cd-player at hand
> (at least connected to my workstation) to test this. So purely from code
> inspection: You set the signal handler before entering el_gets and y
On Thu, 2021-08-12 at 15:57 +0200, Ingo Schwarze wrote:
> Hi,
>
> deraadt@ recently pointed out to me in private mail that it is good
> for usability if interactive programs providing line editing
> functionality are consistent what they do with Ctrl-C, ideally
> discard the current input line and
Hi,
deraadt@ recently pointed out to me in private mail that it is good
for usability if interactive programs providing line editing
functionality are consistent what they do with Ctrl-C, ideally
discard the current input line and provide a fresh prompt.
At least that is what bc(1), ftp(1), sftp(1