KRE> It depends upon the usage. But if you're processing escapes, you
KRE> need to also process \\ to mean a literal '\' of course, [...]
Not necessarily -- '\134' would be good enough :-)
Just joking, of course. The weekend is nigh.
noredrawtags="tags"
noexpandtab magic remap term="screen"
directory="/tmp"
fileencoding="UTF-8"
inputencoding="UTF-8"
matchchars="()[]{}<>"
paragraphs="IPLPPPQPP LIpplpipbp"
recdir="/var/tmp/vi.recover"
sections="NHSHH HUnhsh"
shell="/usr/pkg/bin/tcsh"
shellmeta="~{[*?$`'"\"
Martin Neitzel
h netbsd-host -> vi
NetBSD 8.2_STABLE (GENERIC), amd64, #3: Sat May 2 15:05:24 CEST 2020
/usr/bin/vi,
:ve yields: Version (1.81.6-2013-11-20nb4)
and ts=8
Martin Neitzel
> | The name jot derives in part from iota, a function in APL.
>
> Maybe somebody(tm) should look that up.
That's certainly the case. The other two tools of Kunze's
tool bundle derive from APL, too: rs(1) and lam(1) ("reshape"
and "laminate").
Martin (AP
th that, I don't care much about any
of the other tcsh extras, such as spelling correction. Well,
tcsh's command completion is certainly nice, too, but I wouldn't
kill for that.)
So yes: another vote to "go tcsh!" in base.
Martin Neitzel
Hi Brett,
> So, the point of all this blather is even though there have been no
> interface changes as a result of my work there is the potential for a
> significant visual change. Should I mark this with a libcurses major
> bump? I don't think it necessary but I am putting it out there for
> dis
e(1) gives you all effective values, i.e. after applying
defaults (system and LANG), explicit settings, and an LC_ALL
overrule.
Martin Neitzel
> Anyone?
Yes.
While we are at it: I recently noticed that the NetBSD Guide fails
to even mention YP/NIS in its "NFS" chapter.
http://www.netbsd.org/docs/guide/en/chap-net-services.html#chap-net-services-nfs
Martin Neitzel
Hi Wolfgang,
>> "first $WEEKDAY of next month". I am at a loss how to do this
> $ date -d "$(date -d '+1 month' '+%m/01/%C%y') sat"
> Sat Aug 1 00:00:00 CEST 2020
Nifty -- I would probably never have solved this. Thanks!
Martin Neitzel
9 10
> do
> date -d "+$i month 1 thu"
> done
will not fail immediately but more and more blatantly as we progress
into the month.
Martin Neitzel
PS: The () in the date expressions above are just to illustrate
possible parsings. The actual date command treats "(stuff)" as
a comment.
f getting this oh-so-dreadful
ambiguity in the five initial letters resolved :-)
Martin Neitzel
PS: MUCH more useful to me is a cal(1) option to put Mondays first.
(I use cal(1) daily in the office.)
With the NetBSD cal(1) we can even pull any weekday in front. For
script
't meddle with ownerships
and permissions, and a running daemon can continue to write to the very
same file descriptor.
Martin Neitzel
actually *is* POSIX (and always has been, for both the kill(1)
utility and the kill() function)).
In any case: very worthwhile tutorial -- thanks!
Martin Neitzel
PG> Don't get me wrong, I love apropos(1). But...
PG> I'm continually bitten by the "stemming" that occurs. [...]
So am I. I completely switched over from "man -k" to an alias
effecting "apropos -l" ("legacy"-mode):
% apropos -l lfs
lfs_segwait(2) - wait until a segment is written
lfs_m
Hi Roy,
> * We ship a FTP server in the base system.
> * We supply /var/spool/ftp as a recommened skeletion for anon FTP.
> * We DO NOT supply a ftp user in master.passwd (or group).
>
> Is there a reason for this? Surely we just need to supply a FTP user to
> complete the easy setup of a
t before the "echo".
> So, should we change it?If so, I'll look into what code needs altering.
Yepp, please.
Martin Neitzel
16 matches
Mail list logo