David Binderman | 21 Nov 14:55 2014
Picon

dash-0.5.8 bug report

Hello there,

eval.c:273:19: warning: logical not is only applied to the left hand side of comparison [-Wlogical-not-parentheses]

        if (!exitstatus == isor)

Maybe

        if (exitstatus != isor)

was intended.

Regards

David Binderman

 		 	   		  --
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Stephane Chazelas | 17 Nov 22:49 2014
Picon

command substitutions in $PS4

Hello.

[tested on current git head
f6d4def4e27b13fab174e948b94cd10550d3e10e]

Command substitution doesn't seem to work in $PS4 (used for
xtrace prompt):

$ PS4='$(date +%T)> ' dash -xc :
dash: 1: Syntax error: end of file unexpected (expecting ")")

And with the old syntax:

$ PS4='`date +%T`> ' dash -xc :
> :

And with more than one command:

$ PS4='`date +%T`> ' dash -xc ':;:'
> :

dash doesn't return and seems to go in a forking loop,
presumably because the `date` there triggers another PS4
expansion and so on recursively

If I prevent the recursion with:

--- a/src/eval.c
+++ b/src/eval.c
 <at>  <at>  -776,7 +776,15  <at>  <at>  evalcommand(union node *cmd, int flags)
(Continue reading)

accused81939 | 17 Nov 09:55 2014
Picon

Fix Penguin Penalty 17th October2014 ( mail-archive.com )

Dear Sir

Did your website get hit by Google Penguin update on October 17th 2014? What basically is Google Penguin
Update? It is actually a code name for Google algorithm which aims at decreasing your websites search
engine rankings that violate Google’s guidelines by using black hat SEO techniques to rank your webpage
by giving number of spammy links to the page.

We are one of those few SEO companies that can help you avoid penalties from Google Updates like Penguin and
Panda. Our clients have survived all the previous and present updates with ease. They have never been hit
because we use 100% white hat SEO techniques to rank Webpages.  Simple thing that we do to keep websites away
from any Penguin or Panda penalties is follow Google guidelines and we give Google users the best answers
to their queries.

If you are looking to increase the quality of your websites and to get more targeted traffic or save your
websites from these Google penalties email us back with your interest. 

We will be glad to serve you and help you grow your business.

Regards

Vince G

SEO Manager ( TOB )
B7 Green Avenue, Amritsar 143001 Punjab
____________________________
NO CLICK in the subject to STOP EMAILS
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
(Continue reading)

Stéphane Aulery | 10 Nov 13:12 2014
Picon

(unknown)

Subject Redirection: interval file descriptor (0-9)
Reply-To: 

forwarded 646847 dash <at> vger.kernel.org
stop
-------------------------------------------------------

Hello,

Here is a small patch reported by a user of Debian [1]. Could you please
integrate? Thank you for your help.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646847

Regards,

--

-- 
Stéphane Aulery
Stéphane Aulery | 10 Nov 12:35 2014
Picon

dash.1 - Confusion between two pages c[h]sh

Hello,

Here is a small patch reported by a user of Debian [1]. Could you please
integrate? Thank you for your help.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646847

Regards,

--

-- 
Stéphane Aulery
Attachment (dash.1.fix-chsh.diff): text/x-diff, 231 bytes
Stéphane Aulery | 10 Nov 12:20 2014
Picon

'man dash' typo: "the shell .... proceed onto"

Hello,

Here is a small patch reported by a user of Debian [1]. Could you please
integrate? Thank you for your help.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576503

Regards,

--

-- 
Stéphane Aulery
Attachment (dash.1.typo.diff): text/x-diff, 523 bytes
Stéphane Aulery | 10 Nov 12:19 2014
Picon

dash: details of redirection/duplication in manpage are reversed

forwarded 501566 dash <at> vger.kernel.org
stop
-------------------------------------------------------

Hello,

Here is a small patch reported by a user of Debian [1]. Could you please
integrate? Thank you for your help.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501566

Regards,

--

-- 
Stéphane Aulery
Stéphane Aulery | 10 Nov 12:14 2014
Picon

'man dash' typo: "the shell .... proceed onto"

forwarded 576503 dash <at> vger.kernel.org
stop
-------------------------------------------------------

Hello,

Here is a small patch reported by a user of Debian [1]. Could you please
integrate? Thank you for your help.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576503

Regards,

--

-- 
Stéphane Aulery
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Stephane Chazelas | 5 Nov 12:59 2014
Picon

% in $PATH

Hello,

ash/dash have a nice feature that allows to have:

PATH=/bin:%builtin:/usr/bin:/some/dir%func:/sbin

To have commands in /bin take precedence over builtins and
files in /some/dir being looked up for autoloaded functions (a
bit like FPATH in ksh/zsh).

That's nice but the way it is implemented, that means that %
characters in $PATH cause problems. See for instance:

http://unix.stackexchange.com/questions/126955/percent-in-path-environment-variable

Where someone ran into it when they had a:

/home/torbjorr/deployed/vector/x86_64-GNU%2fLinux directory in
there.

Given than only "builtin" and "func" are recognised after "%", I
think it would be better if the PATH handling accepted any other
string like "foo%bar", "foo%2f", "foo%functions" as-is as a
normal $PATH component.

And foo%2fbar%func meaning "foo%2fbar" treated as a directory
with autoloadable functions.

--

-- 
Stephane
(Continue reading)

Herbert Xu | 5 Nov 09:47 2014
Picon
Picon

[0/3] Minor parser fixes/cleanups

Hi:

The recent discussion on backslash newline led me to some small
fixes and cleanups in the parser which I'm posting now.

Cheers,
--

-- 
Email: Herbert Xu <herbert <at> gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

John Keeping | 1 Nov 18:14 2014
Picon

[PATCH] [BUILTIN] Require leading '0' on octal escapes in echo

printf(1) supports octal escape sequences in its format argument which
are specified as (from POSIX):

	"\ddd", where ddd is a one, two, or three-digit octal number

But the argument to the "%b" format specifier allows:

	"\0ddd", where ddd is a zero, one, two, or three-digit octal
	number

which is similar to the wording for echo(1) (for XSI-conformant
systems):

	\0num	Write an 8-bit value that is the zero, one, two, or
		three-digit octal number num.

Because conv_escape() handles the first case, applying the second
behaviour in conv_escape_str() must also catch the characters '1'-'7' so
that they are not converted as octal numbers.

Signed-off-by: John Keeping <john <at> keeping.me.uk>
---
This was reported several years ago [1] but the patch proposed in that
case seems to have been a bit aggressive and breaks the handling of
"%b".

[1] http://thread.gmane.org/gmane.comp.shells.dash/664

 ChangeLog          | 4 ++++
 src/bltin/printf.c | 5 +++++
(Continue reading)


Gmane