Konversation/FAQ: Difference between revisions
Marked this version for translation |
m several fixes |
||
Line 5: | Line 5: | ||
<!--T:2--> | <!--T:2--> | ||
Pressing <keycap> | Pressing <keycap>Ctrl + M</keycap> will make it re-appear. | ||
It should be noted that most KDE programs follow the same shortcut convention and you should be able to get your menu back this way most of the time. | It should be noted that most KDE programs follow the same shortcut convention and you should be able to get your menu back this way most of the time. | ||
Line 11: | Line 11: | ||
<!--T:4--> | <!--T:4--> | ||
<menuchoice>Settings -> Configure Konversation -> | <menuchoice>Settings -> Configure Konversation -> Behavior -> General -> Enable System Tray</menuchoice> | ||
== I have NetworkManager disabled and connect manually, but Konversation fails to auto-connect and needs restarting == <!--T:5--> | == I have NetworkManager disabled and connect manually, but Konversation fails to auto-connect and needs restarting == <!--T:5--> | ||
Line 30: | Line 30: | ||
<!--T:11--> | <!--T:11--> | ||
Generally, KDE can be told about directories it should consider for retrieval of application resources by filling and exporting the ''$KDEDIR'' or ''$KDEDIRS'' environment variables, and consequently, many distributions make use of this facility. Starting the KDE terminal emulator Konsole and using the ''echo'' command can yield the contents of these variables: | Generally, KDE can be told about directories it should consider for retrieval of application resources by filling and exporting the ''$KDEDIR'' or ''$KDEDIRS'' environment variables, and consequently, many distributions make use of this facility. Starting the KDE terminal emulator [[Special:myLanguage/Konsole|Konsole]] and using the ''echo'' command can yield the contents of these variables: | ||
{{Input|1= echo $KDEDIRS}} | {{Input|1= echo $KDEDIRS}} | ||
Line 38: | Line 38: | ||
<!--T:13--> | <!--T:13--> | ||
In this case, your global '''Konversation''' script folder would be ''/usr/share/apps/konversation/scripts''. If any of these environment variables contains multiple directories | In this case, your global '''Konversation''' script folder would be ''/usr/share/apps/konversation/scripts''. If any of these environment variables contains multiple directories separated by a colon (":"), KDE considers all of them, in the order given. | ||
<!--T:14--> | <!--T:14--> |
Revision as of 14:11, 25 July 2011
Pressing Ctrl + M will make it re-appear. It should be noted that most KDE programs follow the same shortcut convention and you should be able to get your menu back this way most of the time.
My distro turned off the system tray icon, how do I get it back?
I have NetworkManager disabled and connect manually, but Konversation fails to auto-connect and needs restarting
Konversation uses the KDE backend Solid to get network info. To make it reconnect, change the Solid backend to FakeNet.
. Move it to top of the list using the arrows
Apply changes.
Where can I find the scripts included with Konversation (/media, /weather, etc.)?
KDE applications such as Konversation commonly look for their resources in two places, a global directory structure and one located in the home folder of your user account. Each application looks up a directory matching their own name in both places and uses the data within. While ~/.kde/share/apps/konversation/scripts is always picked up by default, the location of the global konversation/scripts folder containing the default selection of scripts shipped with Konversation can be harder to establish, because it depends on the file system layout your distribution has chosen to implement.
Generally, KDE can be told about directories it should consider for retrieval of application resources by filling and exporting the $KDEDIR or $KDEDIRS environment variables, and consequently, many distributions make use of this facility. Starting the KDE terminal emulator Konsole and using the echo command can yield the contents of these variables:
echo $KDEDIRS
Which may output something along the lines of:
/usr
In this case, your global Konversation script folder would be /usr/share/apps/konversation/scripts. If any of these environment variables contains multiple directories separated by a colon (":"), KDE considers all of them, in the order given.
The scripts directory in your home folder - ~/.kde/share/apps/konversation/scripts -, by the way, always has precedence over the global one. So if you want to modify one of the scripts shipped with Konversation for your own purpose, it's good practice to copy it from the global directory to the one local to your user account. This way, an update to Konversation won't overwrite your modifications.
If the above method to retrieve the path of the global scripts folder fails, you can try the output of:
kde4-config --install data
Here are a few more examples of common paths for the global scripts folder in case all of the above methods to retrieve them fail:
/usr/share/apps/konversation/scripts (Gentoo, Kubuntu)
/usr/share/kde4/apps/konversation/scripts
/opt/kde3/share/apps/konversation/scripts (SUSE)
Post version 1.3.1, another way to find out where the installed scripts are is to run this command in Konversation's input line (using the media script as an example, since it comes with any Konversation installation)
/exec --showpath media
How do I make my text bold/italized/underlined?
Examples:
This is my %Bbold%B text.
- This is my bold text.
This is my %Iitalized%I text.
- This is my italized text.
This is my %Uunderlined%U text.
- This is my underlined text.
This is my %Sstruck-out%S text.
- This is my
struck-outtext.
Where is the server list?
Konversation presently doesn't ship with a pre-configured list of known IRC networks and servers. We are planning to provide a place to download and import such lists in the future. In the meantime, on this page you can find a script that will append the contents of mIRC's venerable servers.ini to your Konversation config file.
What is an IRC URL?
Konversation can be started with an URL from the command line. The following URL should work:
Details: (expired IETF draft)