On Mon, Nov 13, 2006 at 03:38:34PM -0700, Bruce Sass wrote:
>
> Kurt, please have a look at:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397073
Dear Mr. Sass,
Thank you for bringing this to my attention. But I don't see why you
need to contact me for this.
The package is group maintained, and alot of other people should already
be receiving your emails. And those people probably know alot more
about this than I do.
I would also like to point out that Sune works on KDE in general, and not
on konsole in specific. KDE is rather big, and you can't know
everything.
You should also be happy that Sune does put alot of time into Debian,
reading bug reports, trying to reproduce it, making suggestions on how
you can solve your problem and so on.
As part of the NM process I will be reviewing how he deals with bug
reports. The only thing I can say is that he's working hard on
making things better.
You seem to be confused to what "interactive" means. Basicly the shell
is interactive if you as user can type commands in it. This has nothing
to do with wether the program (or shell script) that is started by the
shell interacts with the user or not. In case a shell is started
with the "-c" option, it's non-interactive since it will start the
program, and when the program exits so will the shell. You can't type
new commands in the shell after the programs exited.
Anyway, you say it used to work, but it doesn't work anymore. I can see
a few reasons for this:
- Something in konsole changed;
- Something external to konsole changed;
- The way you use it has changed;
- Something else?
In any case it would be useful if you could describe what changed
between the point it worked and the point it stopped working.
Did you do a major upgrade of Debian or KDE? Do you know from what
version to what version? Since this seems to be the latest version, I
assume you have a recent installation, and you can probably use
/var/log/dpkg.log to find the version numbers.
Or you changed window manager, as you seem to mention in a later mail?
And this might be a bug (or feature) of a different WM that you see.
So, after looking a little, I found this code in
kdelibs/kdecore/kprocess.cpp:
if (d->useShell)
{
[...]
arglist[0] = d->shell.data();
arglist[1] = (char *) "-c";
arglist[2] = shellCmd.data();
arglist[3] = 0;
When I start a session, I also see a process with "bash -c
<my command>" with as child a "<my command>".
But I have no idea how it determises to use a shell or
not, but with the case I tried it atleast seems to be
using one. In your case it's probably also using bash,
and that should be easy enough to find out.
It's already been pointed out that starting bash with
-c won't read the .bashrc, so if you want those
environment variables you'll need some other way to set them.
Anyway, I think you misunderstand how things are supposed to work,
and the documentation probably needs to be worded better to avoid
confusion. But you don't seem to be happy about that.
If none of the suggestions work for you, I suggest you
file a (wishlist) bug for the option you like to see. (Or
change this bug to the wishlist bug.)
There might also be a bug in some software, but I'm currently not
conviced this is in konsole or KDE.
With kind regards,
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
