On 20 Jun, martin f krafft wrote:
> mutt allows attaching files from the command-line:
>
> mutt -a /file/one /file/two /file/three -- …
>
> Basically, the rules are: -a takes a list of files, terminated by --.
>
> Zsh's completion of mutt treats the argument to -a as optional:
>
> '*-a[attach
Chris Lamb wrote:
>
> Thanks for applying this. I was wonder if you could also include:
>
> *.changes
> *.dsc
>
> ie. as well as *.deb. All behaviours of path-based .debs can be
> inherited. Thanks in advance :)
Do you mean like the following patch - considering all .changes and .dsc
files
I queried the ast-users mailing iist and both Arch and opensuse
apparently have patches for the issue. See here
http://lists.research.att.com/pipermail/ast-users/2015q3/004773.html
Oliver
This issue was addressed upstream. The fix was included in 5.0.6 and, by
extension, 5.0.7. Let me know if you think there is still something to
address.
Oliver
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Just for your information, this has now been fixed in upstream git.
Oliver
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Just for your information, this has now been fixed in upstream git.
Oliver
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Phi Debian wrote:
It appears after some back and forth mail with attresearch (code
owner) that the source code used by debian (and ubuntu) are both out
of date, they both have this code dump or corruptin bug that was fixed
at ksh93u (dixit David Korn).
Debian does have ksh93u. Latest version
Phi Debian wrote:
On Wed, Oct 9, 2013 at 4:11 PM, Oliver Kiddle okid...@yahoo.co.uk wrote:
Debian does have ksh93u.
Ambiguous
Clearly we've got ambiguity in Debian versions of ksh too:
wheezy does have 2012-02-29, testing/unstable have 2012-08-01. 2012-08-01 will
never go into wheezy
ольга крыжановская wrote:
What is the way to replace the patched up 2012-02-29? Find sponsor,
declare him how bad it is?
I think so.
One thought is that you could try to pester Jonathan Wiltshire
j...@debian.org: he did 93u+-1.2.
It is probably wise to prepare the replacement first.
Oliver
On 4 Oct, you wrote:
How should I proceed for a patch submit, I did provide it to att
owner, so I guess future release will have the fix, but for debian
should I do something, does debian has its own set of 'fixes' (I am
ignorant here)
You an include a small patch in an e-mail to this bug
John Paul Adrian Glaubitz wrote:
Works for me with version 93u+-1.1:
Therefore marked as fixed in 93u+-1.1.
Note that bug 691200 was merged in as a duplicate of this one and the
example in the initial description for that bug is most definitely not
fixed in 93u+-1.1. Issues with cd .. are
John Paul Adrian Glaubitz wrote:
Then you should address the problem as the maintainer of ksh. Since
it's grave bug, it's blocking the release of Debian Wheezy and should
therefore addressed as soon as possible!
The package has been up for adoption for some time because I don't have
the time
Jonathan Wiltshire wrote:
In my opinion, it would be
better if the debian release goes out with either the old squeeze release
(93s+20080202-1) or 93u+20120628-1 (which was only bug fixes).
Well, I think the release team have already expressed that they are less
than happy with having
for packaging the full ast-open set of software.
Thanks
Oliver Kiddle
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: ksh
Version: 93u+-1.1
Justification: renders package unusable
Severity: grave
In many situations, cd .. is broken with this version of ksh. For example,
cd /etc; cd ..
remains in /etc.
Thank you
Oliver Kiddle
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
that I have put the ksh package up for adoption.
Oliver Kiddle
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Mehdi Dogguy wrote:
So intead of reverting a patch [1] and re-open a severity normal bug,
you uploaded a new upstream release [2] ?
I would have classified the original bug as grave too. The upstream
release is a bug fix release: they didn't even change the version number
hence the appended
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Hi,
Please unblock package ksh/93u+20120628-1 which fixes #679966 (severity
grave).
Frankly it would be better to exclude ksh from the next Debian release
than include it with
Zoltan Hidvegi wrote:
More info: this is not an upstream issue, it's caused by the
handle-removed-working-dir.patch which is an attempt to fix
#667038. Besides chopping off the last path component of any cd
../name command, it also does sfprintf(shp-strbuf,oldpwd) which is a
problem if oldpwd
James wrote:
After this morning's upgrade to nmh 1.5-release-0.2, send fails with
post: message has no From: header
post: See default components files for examples
post: re-format message and try again
send: message not delivered to anyone
This is the result of a change in the
Below is a report made via the Debian bug tracking system. I'm guessing
that when handling `..', ksh is trying to use what it previously knew to
be the path to the current directory whereas the other shells aren't
specifying a path.
Oliver
--- Forwarded Message
Date:Tue, 03 Apr 2012
On 25 Nov, Blazej Krzeminski wrote:
Traps set inside KSH functions and 'set -e' (exit on error) command
are ignored when the function is used in a command substitution
and the command substitution $( ) is contained in a || or command,
or is following an 'if'. This problem does not occur in
I'm still unable to reproduce this. It'd be good to have a clearer ide
of your environment.
What edit mode is being used - vi or emacs?
Oliver
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 11 Jul, auto58326...@hushmail.com wrote:
Problem:
When issuing the fc command, the program searches for /bin/ed which
doesn't exist in recent default debian installs.
I'm concerned that changing the default is unwise because some user's
may be used to it being the default. I always
Can you still reproduce this? I'm still be unable to.
Any chance of a core file? Without one, I don't really have a hope of
fixing it.
Oliver
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Following is a bug reported to the Debian bug tracking system.
--- Forwarded Message
Date:Thu, 04 Aug 2011 18:42:18 +0900
From:SATOH Fumiyasu fumi...@osstech.co.jp
To: sub...@bugs.debian.org
Subject: Bug#636580: ksh: ${-#pattern} fails in set -u mode
Package: ksh
Version: 93u-1
I'm also experiencing exactly this problem on a fully updated Debian
testing system. It broke at about the point the kernel was upgraded
from 2.6.32 to 2.6.38. I've not got any non-default grub options that
I'm aware of. I've got a fairly old PCI Matrox G450 graphics card so no
support for kernel
The following has been sent to the Debian bug tracker for ksh.
--- Forwarded Message
Date:Wed, 01 Dec 2010 23:56:39 +0100
From:=?UTF-8?Q?Pawe=C5=82?= Kalinowski anilatx+deb...@gmail.com
To: Debian Bug Tracking System sub...@bugs.debian.org
Subject: Bug#605630: ksh: Unreasonable
Package: halevt
Version: 0.1.6.2-1.4
Severity: normal
The post installation script appears to be failing when I install halevt.
The problem is with the following line:
invoke-rc.d --quiet hal restart
This is returning status 100 because there is no /etc/init.d/hal
Is there a missing package
Jeff Green wrote:
% XXX=hello /bin/echo $XXX
When the shell see's this line, it expands $XXX itself first. It is not
/bin/echo doing the expansion.
Note that if you do the following, it will print hello.
XXX=hello printenv XXX
Oliver
--
To UNSUBSCRIBE, email to
Jeffrey B. Green wrote:
The question is then: what do users do with the explanation on the
manpage? I.e. they are not equivalent since the results are not the same.
But they are equivalent as far as the above execution of cmd is
concerned. When you run XXX=hello /bin/echo $XXX, the echo
Jeffrey B. Green wrote:
My assumption is that two forms said to be equivalent imply the results
of the forms are identical, they can be substituted for each other.
Otherwise, they not not equivalent, just similar. What is your
definition of equivalent?
But the man page doesn't just say
The following issue has been reported for the Debian package.
After completion, ksh appears to repeat just the last line of the PS1
prompt. In the case of this coloured prompt, it is outputting:
cresc[0;33m[escesc[0m156esc[0;33m]escesc[0m$ clcr
So why the duplicated escape characters?
Thanks
I tried rebuilding from source because I have an amd64 system.
You're missing a build dependency on libqt4-dev which it needs for moc-qt4.
With that installed, it build and installed on amd64.
Still can't get the WMS plugin to work though - just red boxes
containing Exception occurred. What do
not be used. My bookmarks file ends up having lines such as:
-e http://www.independent.co.uk/ news
Thank you
Oliver Kiddle
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32
It seems to be fixed in the 2010 version, e.g.
It looks like you can close this bug.
Thanks for checking.
Oliver
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 20 Oct, Jeff Green wrote:
$ cati
So are you saying that on that line, no key other than newline does
anything?
The blank input line for the 2nd cati invocation basically is
ignoring all input except a newline. Once the newline is entered,
the shell recognizes input again.
I've not been
these errors are occurring?
Thank you
Oliver Kiddle
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 16 May, you wrote:
Package: ksh
Version: 93t+-1
Severity: serious
There was an error while trying to autobuild your package:
I can't reproduce this on armel or amd64.
Is there anything unusual about your build machine. In particular, what
shell in /bin/sh? Not working with pdksh derived
Samuel Thibault wrote:
Clint Adams, le Sat 26 Apr 2008 16:05:48 +0100, a écrit :
Having locale-based (and multibyte) word separators sounds like a nightmare
to me, but maybe someone has some ideas.
iswspace()
The characters used for word splitting are contained in the IFS
variable. So you
Vincent Lefevre wrote:
As you can see, the ksh93 printf builtin doesn't behave like the
coreutils printf, and this is ksh93 which is wrong. Indeed, the
field width and the precision are number of bytes, not number of
characters.
Thanks for the report but in this case, I really think the
Clint Adams wrote:
On Thu, Dec 06, 2007 at 05:56:12PM +0100, Dr. Markus Waldeck wrote:
Please correct _cut as mentioned in my mail from Fri, 16 Nov 2007 10:16:44
+0100.
Okay, but it is certainly ugly.
You can use $'\u00e4' which wouldn't be quite so ugly.
Oliver
--
To UNSUBSCRIBE,
You wrote:
Package: ksh
Version: 93s+20070628-1
Severity: wishlist
http://www.research.att.com/~gsf/download/release.2007-11-05.2007-03-28.html
No, you may not have it yet but 20071105 has already been uploaded to
sid.
Would be nice if you could upgrade to it and verify that bug 304365 is
On 13 Jul, Diab Jerius wrote:
Setting and unsetting emacs mode in a particular manner causes a
segmentation fault. My .profile file contains the single line
set -o emacs
I can't reproduce this but I don't have access to an amd64 system. So
I'll need your help to resolve it. Do you have any
On 30 Jun, Josh Hurst wrote:
06-10-15 The remaining math functions from C99 were added for any system
that supports them.
Please compile the package with -std=gnu99 to get this math support
Are you sure that -std=gnu99 is necessary? There are definitely new math
functions available
Adam Megacz wrote:
You should include a dummy file in the archive for each of these. The
dummy file can be empty (ie zero bytes long) if necessary. Then make
sure that the process which creates them during postinst doesn't
complain about the fact that they're already there.
Is that really
--- Josh Hurst [EMAIL PROTECTED] wrote:
This bug can be fixed by updating to ksh s+, add -DSHOPT_SYSRC to the
build flags and add a file called /etc/ksh.kshrc with the content
cut cut cut
set -o gmacs
Is this really the problem in this case? The up arrows and tab key work
--- W. Borgert [EMAIL PROTECTED] wrote:
On Wed, Apr 18, 2007 at 07:51:31PM +0200, Daniel Leidert wrote:
What is the current state of the ITP of xmlroff, Oliver? What is
As far as I was concerned, I had handed it to Wolfgang.
There was a long time of no visible activity upstream, but there
On 14 Apr, Clint wrote:
On Sun, Oct 22, 2006 at 12:22:37AM +0200, Jörg Sommer wrote:
% date --verTAB
--version-- Versionsinformation anzeigen und beenden
% date --ver
but the text is not completed.
This improves things slightly.
This is what _guard is for. Use something like:
On 21 Jul, Josh Hurst wrote:
RFE: ksh93 should be installed as /bin/ksh by default to match SuSE,
Can I close this bug? As far as I'm concerned, this is default because
ksh93 is the highest priority package providing /bin/ksh via the
alternates system (see my earlier reply).
Oliver
--
To
--- Norman Ramsey [EMAIL PROTECTED] wrote:
David Korn reports that this bug is fixed upstream in the 'ksh 93r+'
version on the web. A Debian update would be lovely.
That's an alpha release though isn't it? There's a few other fixes in
that but probably at least as many new bugs. I was
--- W. Borgert [EMAIL PROTECTED] wrote:
are you working on the Debian packaging of xmlroff? If not, I
would like to package xmlroff with the XML/SGML group as
maintainer, if the team does not object. Of course, you could
join the team, btw.
I was working on it. I had a package before the
--- Julien Danjou [EMAIL PROTECTED] wrote:
ksh fails to build, however I guess this is caused by /bin/sh linked
to /bin/dash.
If you really need bash and don't use only POSIX compliant syntax,
please call /bin/bash instead of sh.
Actually, more likely this is dash failing to be POSIX
Josh Hurst wrote:
RFE: ksh93 should be installed as /bin/ksh by default to match SuSE,
Fedora, Darwin, SCO Unix, and AIX5L which all install ksh93 as
/bin/ksh.
Under unstable/testing, /bin/ksh is a symbolic link that is handled by
the alternates system. ksh93 is the highest priority package
On 25 May, Joerg Sommer wrote:
can you add completion support for svn diff? If I understand it right, it
should be the same rule like commit -- all files they are known by svn
are able to be used with diff.
The patch below should fix this and bug 342348. The diff subcommand can
also take
--- Martin Michlmayr [EMAIL PROTECTED] wrote:
This package fails to build on AMD64. I cannot quite figure out why,
but it seems the md5 file is never generated.
I notice that, looking at the build logs, there is a successful build
later on. See:
Package: spamprobe
Version: 1.2a-1
Severity: wishlist
http://prdownloads.sourceforge.net/spamprobe/spamprobe-1.4b.tar.gz
There's been a number of new releases since the debian package was last
updated. Would be nice to have an update to the package.
Oliver Kiddle
This e-mail and any
Nicolas Duboc wrote:
I have actually packaged this 1.4b version this week-end. I'm currently
testing it on my own configuration. I planned to upload tomorrow if I
find no problem.
Excellent. That's good to hear. Thanks
Oliver
This e-mail and any attachment is for authorised use by the
Package: wnpp
Severity: wishlist
* Package name: pangoxsl
Version : 1.6.0.1
Upstream Author : Tony Graham [EMAIL PROTECTED]
* URL : http://sourceforge.net/projects/pangopdf/
* License : LGPL
Description : additional XSL atttributes for Pango
PangoXSL
utilities (such as nmake etc) could be built from one source
package.
Oliver Kiddle
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied
Package: kimberlite
Version: 1.1.0-3.3
Severity: normal
kimberlite depends on pdksh and includes ksh scripts in
/usr/lib/kimberlite that rely on #!/bin/ksh to run the scripts. However,
since version 5.2.14-18 of pdksh, pdksh is installed as /bin/pdksh and
the alternates system used to handle
Package: flowscan
Version: 1.006-8
Severity: normal
This package depends on pdksh and as far as I can tell, uses /bin/ksh.
However, since version 5.2.14-18 of pdksh, pdksh is installed as
/bin/pdksh and the alternates system used to handle /bin/ksh. Upstream
suggests that either real ksh or pdksh
Mark Brown wrote:
The solution was to temporarily run ypbind. It seems that yppush trys
to find out the list of slaves from ypbind. As this is a master and is
not a NIS client itself, this fails. It should be able to just look in
/var/yp/ypservers.
Is there some reason why you
On 30 Sep, Clint Adams wrote:
I'll put umask 022 in /etc/skel/.zshrc, I suppose.
It would be better to put that in one of zprofile or zlogin. It is
exported to child processes and it could be a nuisance (or even a security
risk) if child shells override the setting.
Oliver
This e-mail and
You wrote:
For svn revert, when I complete a deleted file, the space isn't
added after the filename. There's no such problem with modified
files (marked with 'M') for instance.
This isn't actually an _subversion issue but a more fundamental file
completion issue. Filename completion adds a
You wrote:
The subversion case is a bit special. Even if the removed item was a
directory, the suffix should be a space, not a slash, because AFAIK,
doing svn revert on an item inside a removed directory has not much
sense.
We could try passing -S ' ' to _files. Perhaps try adding that in
. hostname alone returns debian and no error.
Thanks
Oliver Kiddle
This message has been scanned for viruses by MailControl - www.mailcontrol.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
You wrote:
It appears that ksh93 is not respecting the \c (suppress trailing
newline) in an echo statement - for example:
#!/bin/ksh
echo enter a number = \c
output is:
enter a number = \c
This is by design. See the man page. In particular:
echo [ arg ... ]
When the first arg
You wrote:
This version of zsh breaks subversion completion for svn ci:
% svn ci
_svn:42: unknown file attribute
Oops. That's my fault. Sorry about that. Fix is below:
Index: _subversion
===
RCS file:
On 17 Jun, you wrote:
Package: ksh
Version: 93q-3
Severity: normal
Tags: patch
When building 'ksh' on amd64/unstable with gcc-4.0,
I get the following error:
This has apparently been fixed upstream. Without access to the correct
fix, I'll wait for the release of 93r.
Oliver
This e-mail
On 17 Jun, you wrote:
With the attached patch 'ksh' can be compiled
on amd64 using gcc-4.0.
I'm a little reluctant to simply apply this patch without understanding
what's going on better. Is this a gcc-4.0 or amd64 issue, or something
that really is specific to both. What affect does the
Bart wrote:
(Google indicates that ksh does run
on UNICOS; I wonder what it does with ERR in that case.)
I tried asking on ast-users and received the following answer from Glenn
Fowler:
| ksh does not currently handle this
| but I talked with David Korn and the next release will do the
IMHO, this can only lead to confusion. if one installs zsh as ksh, he
might use commands that are not supported by historical ksh,
and historical scripts may not run.
Quite frankly there is no shell in Debian which perfectly emulates
historical ksh. The newer versions of ATT ksh could break
[EMAIL PROTECTED] wrote:
Again, why can't you stop wasting everybody's time instead of RTFM like
I suggested in my first reply?
I have RTFM and I don't see how it helps. The readme file you pointed to
doesn't even mention udev.
I'll quote the udev web page:
It is recommended that you also
[EMAIL PROTECTED] wrote:
HOTPLUG_RC_$SUBSYSTEM
If set to no, disables coldplugging for the $SUBSYSTEM.
Thanks but this isn't really the point of why I raised a wishlist item
in the bug tracker. I had already done update-rc.d -f hotplug remove
which presumably has the same effect.
Package: udev
Version: 0.056-2
Severity: wishlist
Reading various FAQs etc on the web, it seems clear that udev can work
fine without hotplug. It also seems that other distributions allow
udev to be used without hotplug. I really don't want to use hotplug:
it takes ages at bootup, loads modules
Greg KH wrote:
Reading various FAQs etc on the web, it seems clear that udev can work
fine without hotplug.
Huh? That is not true. Please point me at those faqs. The kernel
_MUST_ support hotplug for udev to work properly.
I'm talking about the hotplug scripts not CONFIG_HOTPLUG in
[EMAIL PROTECTED] wrote:
It is also annoying because hotplug depends on usbutils and my machine
doesn't even have USB.
It does not:
Depends: module-init-tools | modutils (= 2.4.2), debconf (= 0.2.26),
procps, grep (= 2.5.1.ds1-2), sed (= 4), bash (= 2.05b-1)
Sorry, I was looking at
Greg KH wrote:
See http://www.gentoo.org/doc/en/udev-guide.xml
hotplug-base is NOT the hotplug/coldplug startup stuff. You want that
file. Why would you not?
That's what I was assuming. The trouble is that in Debian there is no
hotplug-base. udev depends on the hotplug package and that
You wrote:
Does your terminal simply generate a Ctrl-I for tab?
It moves my cursor about 8 characters. Ctrl-L generates ^L . Ctrl-D exits
from that shell. UpArrow generates ^[[A .
If you run cat -T, then press tabenterctrl-d, does it print ^I. If
^[[A for up arrow doesn't work then it
Juhapekka Tolvanen wrote:
Package: zsh
Version: 4.2.5-1
Severity: wishlist
Packager of pdksh realised that and made
Or to be more precise, Clint raised a bug on pdksh.
Hence, I propose also zsh will use update-alternatives for managing
that ksh-symlink. I also propose that a package
You wrote:
Package: ksh
Version: 93q-1
Severity: normal
If I hit ArrowUp -key in ksh93, it do not bring the last command from
history. If I hit TAB or ESCESC , it do not work as Tab
completion at all.
They work for me.
Does your terminal simply generate a Ctrl-I for tab?
You're only
This patch should fix it.
Oliver
Index: sbr/folder_read.c
===
RCS file: /cvsroot/nmh/nmh/sbr/folder_read.c,v
retrieving revision 1.2
diff -u -r1.2 folder_read.c
--- sbr/folder_read.c 2 Jul 2002 22:09:14 - 1.2
+++
Package: wnpp
Severity: wishlist
* Package name: ksh
Version : 93q
* URL : http://www.kornshell.com/
* License : Common Public License (CPL) Version 1.0
Description : The real ATT Korn shell
The latest version of ATT Software Technology's (David Korn's)
84 matches
Mail list logo
