Re: tcsh's exit codes
rank1see...@gmail.com wrote: There is something wrong with tcsh shell: # mergemaster -V | grep '\--run-updates' Returned exit code 1 # mergemaster -V | grep -q '\--run-updates' Returned exit code 141 I believe this has been a feature of csh and tcsh since the dark ages. Negative status codes propagate through pipelines (and through backtick sub-commands as well). In fact the returned $status value is the value of the last command that returned an error (non-zero) status code. This makes it easy to determine if a pipeline command sequence has failed. The 141 status code indicates a sigpipe: the pipeline was not completely read (as described in the grep manual for this case). This also is the common exit code when using head(1) for example. This error-propagation behaviour can be suppessed with 'unset anyerror' in tcsh. In that case it should work as you expect. But note that your commands are no longer compatible with 'good old' csh behaviour then. Regards, Johan pgpPINcqryZSe.pgp Description: PGP signature
Re: [GSoC] About the idea: Unicode support in vi
Zhihao Yuan wrote: Could you please eleborate on the nvi-devel problems? I'm the current maintainer of this port, and as far as I know it's fully functional. 1. It does not support non-Unicode encodings. Actually, these encodings are mainstream in multi-byte encodings world. A proper iconv-awared implementation should be able to handle all of the encodings in `iconv -l`; 2. It depends on DB3/4. We won't accept DB3/4 in base system and we won't accept nvi-devel. 3. It's not 100% compatible with nvi 1.79. Thank you for explaining. Indeed, all valid points and I fully agree that nvi-devel is not fit for inclusion in base as it is. In fact, the nvi from base is probably a better starting point (than nvi-devel) to create an editor that is fully compatible with nvi 1.79 and supports all multi-byte encodings. And when you, or someone, else creates such an editor, I will be pleased to remove the obsoleted port of nvi-devel. Johan pgpdrm84mqX2I.pgp Description: PGP signature
Re: [GSoC] About the idea: Unicode support in vi
Zhihao Yuan wrote: 2. nvi does not use iconv, nvi-m17n only supports limited non-Unicode mbyte encodings, nvi-devel has too many problems. So we don't have a nvi which comes with fully mbyte enconding support; Could you please eleborate on the nvi-devel problems? I'm the current maintainer of this port, and as far as I know it's fully functional. nvi-devel does have proper UTF-8 support via libiconv. It is based on the nvi version we currently have in base and much of the code base is still identical. Johan pgpEar3ZsAfUZ.pgp Description: PGP signature
Re: Problem in bin/sh stripping the * character through ${expansion%}
Doug Barton wrote:
I came across this problem during a recent portmaster update. When
trying to strip off the * character using variable expansion in bin/sh
it doesn't work. Other special characters do work if they are
properly escaped.
Your script does
var=${var%\*}
When I tried it myself, I automatically typed quotes, which does work
var=${var%\*}
Alternatively you could use (with or without quotes)
var=${var%[*]}
Still, I don't see a reason why your variant shouldn't work as well..
Regards,
Johan
pgpF040hK1k5O.pgp
Description: PGP signature
Re: Problem in bin/sh stripping the * character through ${expansion%}
Johan van Selst wrote:
When I tried it myself, I automatically typed quotes, which does work
var=${var%\*}
Really should learn to read better: this in fact procudes 'foo'
rather than 'foo\' in the given example case. Again, not like bash.
Johan
pgpbI94sMye6i.pgp
Description: PGP signature
Re: small usr.bin/find patch
Alexander Best wrote: hmmm...but dd e.g. uses lowercase instead of upercase letters to indicate kilobyte, megabyte and so on. isn't there some unix/posix/whatever standard telling app developers what to use? It might be appropriate to use expand_number() here. This is what some other tools do as well and consistency between tools is a nice thing. Ciao, Johan pgpKTqoLnneUY.pgp Description: PGP signature
Re: does Copyright on source files expire ?
Luigi Rizzo wrote: I said yes, but then I was wondering what happens if the person listed is not responding or not reachable anymore: does copyright on source code expire, and if so, when ? Yes, copyright expires. When it expires exactly depends on local legislation. Generally this is a number of years after the death of the longest living author. I believe in the US copyright generally expires 70 years after the death - or if the copyright is owned by a company, then it expires 120 years after creation (or 95 years after publication). There is a lot of documentation about copyright details available on the internet - but keep in mind that laws change frequently. So it's probably safe to assume that all code used in FreeBSD is still covered by copyright and all licenses granted by the authors still apply (untill one day the copyright expires). P.S. As with all legal stuff, there are always exceptions to the rule: specific cases and local legislation may differ a lot. Ciao, Johan pgpYDNMllMjxj.pgp Description: PGP signature
Re: tcsh fix
Kevin Lyons wrote: Presumably pure csh is the last stable release of csh before tcsh came along. Openbsd, netbsd, sun and sgi all seem to have been able to settle on a csh. If you really want csh, please install ports:shells/44bsd-csh/ And if you just want to troll, please stop. Thank you. Greetings, Johan pgpG9ro9TyRgD.pgp Description: PGP signature
