Repeating configuration of Kate or Kwrite, how?

[John Bee]

John Bee
Oh no, I figured that out no problem, because when pasted in the line dispeared off the screen.

Here is my .bashrc

Code: [Select]

# .bashrc

# User specific aliases and functions
alias cd~='cd ~'
#alias su='su -'
alias ndl='cd /home/data/NetDLoads'
alias grep='grep -i'

ds () {
echo Disk Space Utilization For $HOSTNAME
df -h
}

# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi

#JB: I added the following
# If you're the type who wants to pack your prompt full of information, then here's the one for you.
# This one is a multi-line prompt containing date/time, full path, user and host, active terminal, even file count and space usage.
# if you want to insert a space, just escape it. Enter as slash space - '\ '

PS1="\n\[\033[1;35m\]\$(/bin/date +%a\ %b\ %e\ %r\ %Z\ %Y)\n\[\033[0;36m\]\w\n\[\033[1;32m\]\u@\h: \[\033[1;34m\] \[\033[1;36m\]\$(/bin/ls -1 | /usr/bin/wc -l | /bin/sed 's: ::g') items \[\033[1;33m\]\$(/bin/ls -lah | /bin/grep -m 1 total | /bin/sed 's/total //')b\[\033[0m\] -> \[\033[0m\]"

export LESS_TERMCAP_mb=$'\E[01;31m'
export LESS_TERMCAP_md=$'\E[01;31m'
export LESS_TERMCAP_me=$'\E[0m'
export LESS_TERMCAP_se=$'\E[0m'
export LESS_TERMCAP_so=$'\E[01;44;33m'
export LESS_TERMCAP_ue=$'\E[0m'
export LESS_TERMCAP_us=$'\E[01;32m'

This does use external commands to gather data on the line, specifically sed, ls, wc, which I think is standard stuff, but you may want to check to make sure you have them.

I would do a pic to show you what it looks like, but as I am on dial-up.... 

[Old-Polack]

old-polack
Thank you, went to try it out right away loved the little hint above konsole opening method.  Seems I headed right into a surprise

Code: [Select]

[root@localhost gert]# kwrite .bashrc
kwrite(23191): Session bus not found

KCrash: Application 'kwrite' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde4/socket-localhost.localdomain/kdeinit4__0

[1]+  Stopped                 kwrite .bashrc
[root@localhost gert]# kwrite

The message pops up and I can copy from the ladybird bug window

"Executable: kwrite PID: 26760 Signal: 6 (Aborted)"

I think I need to think about installing crash debugger as the log is empty or can't be created or something, nice looking red bug though

Anyone got any suggestions?  I have used konsole this way of opening kwrite as as late as 24 hours ago? This is getting interesting again.

You ran the command as root, not your normal user. It's the normal user's prompt you want changed, not root's, so you need to change the /home/<you>/.bashrc file, not the one in /root.

Try again as your normal user, without doing su.  



I partially closed the windows to make sure the screen shot wasn't too big, but you get the idea. After you copy/paste the lines, press the Enter key to start a new line, then save the file. System files must always end with a blank new line to function properly.

When you open a new terminal window, the prompt should be as you see mine, but with your user name, not polack.

[wedgetail]

old-polack
Thank you, I am getting there.  The only reason I used root was because it happened to be open, did not even think about I might get 'his' .bashrc, so I am now glad the it failed.  That empty last line well, totally forgotten about that.

Your way is working fine now and I like the options to set up some really good contrasting  combinations. (John BEE will have to wait until need a challenge to decode, does not work at all)

I noticed when I checked right now and changed to light blue that I have not had the last line empty, but it was a comment line.  Can it be that the empty line after each of your selections will safeguard operation in such a case, my thinking the comments would have no influence on running 

Can I add something in your lines to define the background colour ?  I remember when in pclos2009 I went to my dt6 I had 4 terminal popping up on start, two su and two normal, the su were waiting on password and had light yellow/brown background. I am pretty sure that would have been you instructions at the time as I was not too sure what I was doing. Now I know it can be done but forget where, oh what fun.

[Old-Polack]

old-polack
Thank you, I am getting there.  The only reason I used root was because it happened to be open, did not even think about I might get 'his' .bashrc, so I am now glad the it failed.  That empty last line well, totally forgotten about that.

Your way is working fine now and I like the options to set up some really good contrasting  combinations. (John BEE will have to wait until need a challenge to decode, does not work at all)

I noticed when I checked right now and changed to light blue that I have not had the last line empty, but it was a comment line.  Can it be that the empty line after each of your selections will safeguard operation in such a case, my thinking the comments would have no influence on running 

Can I add something in your lines to define the background colour ?  I remember when in pclos2009 I went to my dt6 I had 4 terminal popping up on start, two su and two normal, the su were waiting on password and had light yellow/brown background. I am pretty sure that would have been you instructions at the time as I was not too sure what I was doing. Now I know it can be done but forget where, oh what fun.

Maybe here?

http://www.pclinuxos.com/forum/index.php/topic,71397.msg591547.html#msg591547

[wedgetail]

old-polack
Thank you, not only did I get the colours but a heap of other explanations. I notice that was when I was on my summer break. Looks like I did loose a lot of fun and information. I will experiment tomorrow.

[Old-Polack]

old-polack
Thank you, not only did I get the colours but a heap of other explanations. I notice that was when I was on my summer break. Looks like I did loose a lot of fun and information. I will experiment tomorrow.

The place where the choice of which type konsole tab to open has changed since that was written, so poke about a bit to find it. I'm on the old system now so can't post a screen shot of the change. Other than that all should still be the same.

[wedgetail]

old-polack
I am just parking this snippet here, so I can look at it later:  What happened I was wondering where the 'klipper.exe' was and was going to peek inside. Found something via locate and dumped it on command line.  Now I have two klippers the scissor one and the old icon one, actually the presentation is nicer and sharper all round in the new one.

Code: [Select]

[root@localhost ~]# /usr/bin/klipper
QSystemTrayIcon::setVisible: No Icon set
kdeinit4: Shutting down running client.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
KDE Daemon (kded) already running.
kbuildsycoca4 running...
kbuildsycoca4(27119) parseLayoutNode: The menu spec file contains a Layout or DefaultLayout tag without the mandatory Merge tag inside. Please fix your file.
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.26'
klipper(27103) KGlobalAccelPrivate::_k_serviceOwnerChanged: detected kglobalaccel restarting, re-registering all shortcut keys
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
[root@localhost ~]# QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()

I did not mean to do this? Any idea why I got a different looking Klipper? Really is too late for me.

Just seen your latest about looking around, no problem.  ZZZzzzzz...