11 a.m.
I love the way that Dolphin can now be set up so that it has a console
at the bottom that follows the directories as you browse. I often
browse somewhere and then do command line commands and then do something
with a GUI and then... back and forth. Its an excellent way to work.
Whoever thought of tying Dophin and a console together deserves a medal.
However, I find one part of it to be annoying... whenever you change a
directory in Dolphin, it records a cd command in the console history.
I really like how the console tracks the directory changes that occur in
Dolphin. It saves me a lot of time, not having to issue cds in the
console to keep it in the directory that I am looking at in Dolphin.
However, it might be me, but I don't want to see the Dolphin cds in the
console history. The only commands that I want to see in the console
history are the ones that I enter myself manually. If I want to note
what directory I am working in in the console history, I'll issue a pwd
command.
I think it would be really nice if there was a turn off the logging of
Dolphin cds in the console history. Is there a way to do this ?
Another issue is how there is only one console tied to the Dolphin app
and yet Dolphin can have a split screen with 2 different directory
views. Unfortunately, every time you jump between views another cd gets
issued in the console.
It would be nice if a split view Dolphin session had 2 consoles. It
would be really nice if those sessions shared the same history so that
if you typed a command in one, you could just put the cursor in the
other console, go into the history and repeat the same command in the
other console.
I love open source and Fedora and KDE.
Thanks for listening.
1:45 p.m.
On Wednesday 13 May 2009 17:00:59 Linuxguy123 wrote:
It would be nice if a split view Dolphin session had 2 consoles. It
would be really nice if those sessions shared the same history so that
if you typed a command in one, you could just put the cursor in the
other console, go into the history and repeat the same command in the
other console.
Have you considered filing a RFE for this? It sounds like an enhancement that
quite a few folk would enjoy.
Anne
--
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature? Add it to UserBase
10:41 a.m.
On Wed, 2009-05-13 at 19:45 +0100, Anne Wilson wrote:
On Wednesday 13 May 2009 17:00:59 Linuxguy123 wrote:
> It would be nice if a split view Dolphin session had 2 consoles. It
> would be really nice if those sessions shared the same history so that
> if you typed a command in one, you could just put the cursor in the
> other console, go into the history and repeat the same command in the
> other console.
Have you considered filing a RFE for this? It sounds like an enhancement that
quite a few folk would enjoy.
I am interested to hear what others think of my suggestion. I find a
console attached to Dolphin incredibly useful. In the past I usually
had separate browser and console apps. Linking them makes things so
much nicer.
2:28 p.m.
On Wed, 2009-05-13 at 10:00 -0600, Linuxguy123 wrote:
However, it might be me, but I don't want to see the Dolphin cds
in
the console history. The only commands that I want to see in the
console history are the ones that I enter myself manually. If I want
to note what directory I am working in in the console history, I'll
issue a pwd command.
The console is just running a Shell, so there may be a way to
approximate what you want -- such as ignoring "cd" commands -- using
HISTCONTROL and HISTIGNORE environment variables (see bash(1)). However
these would apply to all your Shell sessions and AFAIK there's no way to
distinguish between manually and programatically entered input.
poc
10:47 a.m.
On Wed, 2009-05-13 at 14:58 -0430, Patrick O'Callaghan wrote:
On Wed, 2009-05-13 at 10:00 -0600, Linuxguy123 wrote:
> However, it might be me, but I don't want to see the Dolphin cds in
> the console history. The only commands that I want to see in the
> console history are the ones that I enter myself manually. If I want
> to note what directory I am working in in the console history, I'll
> issue a pwd command.
The console is just running a Shell, so there may be a way to
approximate what you want -- such as ignoring "cd" commands -- using
HISTCONTROL and HISTIGNORE environment variables (see bash(1)). However
these would apply to all your Shell sessions and AFAIK there's no way to
distinguish between manually and programatically entered input.
One way to handle this might be to "open" a new console (transparently)
in a different directory every time that Dolphin does a dir change.
That way a cd is never issued in the console.
Another way would be to add a switch to cd/bash such that it doesn't log
in history.
Another way would be to add a sync checkbox to top of the console pane
such that one could surf around in Dolphin and then check sync at which
time console would cd to where Dolphin is and cd whenever Dolphin does.
One could then unsync whenever one wanted to keep the console in one
place and Dolphin in another. This would be a really nice enhancement
too, especially if Dolphin stored the state of the sync setting in
between sessions. Ie start unsynced for general browsing and then let
the use sync up when s/he wants.
So many ways to make this super application even more versatile.
LG
5454
days inactive
5455
days old
5 comments
3 participants
participants (3)
-
Anne Wilson -
linux guy -
Patrick O'Callaghan