Konversation/FAQ: Difference between revisions

From KDE UserBase Wiki
(Marked this version for translation)
(Remove FORCETOC magic word; the page has sufficient headings to always have a TOC)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<languages />
<languages />
__FORCETOC__


<translate>
<translate>
Line 6: Line 5:


<!--T:2-->
<!--T:2-->
Pressing <keycap>Ctrl + M</keycap> will make it re-appear.
Pressing <keycap>Ctrl + M</keycap> will make it re-appear. It should be noted that most KDE applications follow the standardized shortcut convention, and you should be able to restore your menu to its default assignments 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.


== My distro turned off the system tray icon, how do I get it back? == <!--T:3-->
== My distro turned off the system tray icon, how do I get it back? == <!--T:3-->


<!--T:4-->
<!--T:4-->
<menuchoice>Settings -> Configure Konversation -> Behavior -> General -> Enable System Tray</menuchoice>
<menuchoice>Settings</menuchoice> → <menuchoice>Configure Konversation</menuchoice> → <menuchoice>Behavior</menuchoice> → <menuchoice>General</menuchoice> → <menuchoice>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-->


<!--T:6-->
<!--T:6-->
'''Konversation''' uses the KDE backend [[Special:myLanguage/Glossary#Solid|Solid]] to get network info. To make it reconnect, change the Solid backend to FakeNet.
'''[[Konversation]]''' uses the KDE [[Special:myLanguage/Glossary#Solid|Solid (glossary entry)]] backend to get network info. To make it reconnect, change the Solid backend to FakeNet.


<!--T:7-->
<!--T:7-->
<menuchoice>System Settings -> Advanced tab -> Hardware ->Network -> FakeNet</menuchoice>. Move it to top of the list using the arrows
<menuchoice>System Settings</menuchoice> → <menuchoice>Advanced tab</menuchoice> → <menuchoice>Hardware</menuchoice> → <menuchoice>Network</menuchoice> → <menuchoice>FakeNet</menuchoice>, and move it to the top of the list using the arrows.


<!--T:8-->
<!--T:8-->
Line 26: Line 24:


<!--T:33-->
<!--T:33-->
{{Note|1=Since KDE SC 4.5, this setting is found in the '''Network Management Backend''' section of <menuchoice>System Settings -> Hardware -> Information Sources</menuchoice>.}}
{{Note|1=Since KDE SC 4.5, this setting is found in the '''<menuchoice>Network Management Backend</menuchoice>''' section of <menuchoice>System Settings</menuchoice> → <menuchoice>Hardware</menuchoice> → <menuchoice>Information Sources</menuchoice>.}}


== Where can I find the scripts included with Konversation (/media, /weather, etc.)? == <!--T:9-->
== Where can I find the scripts included with Konversation (/media, /weather, etc.)? == <!--T:9-->


<!--T:10-->
<!--T:10-->
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 <tt>~/.kde/share/apps/konversation/scripts</tt> is always picked up by default, the location of the global <tt>konversation/scripts</tt> 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.
KDE applications commonly look for their resources in two places, and '''Konversation''' is no exception to this. First they search a '''global''' directory structure, and then another one called '''user''', 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 <kbd>~/.kde/share/apps/konversation/scripts</kbd> is always picked up by default, the location of the global <kbd>konversation/scripts</kbd> folder containing the default values for all scripts shipped with '''Konversation''' can be harder to establish, because it depends on how the filesystem your distribution has chosen to implement is laid out.


<!--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 [[Special:myLanguage/Konsole|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 <kbd>$KDEDIR</kbd> or <kbd>$KDEDIRS</kbd> environment variables, and consequently, many distributions make use of this facility. Starting the KDE terminal emulator [[Special:myLanguage/Konsole|Konsole]] and using the <code>echo</code> command can yield the contents of these variables:
{{Input|1= echo $KDEDIRS}}
<syntaxhighlight lang="shell" highlight="3">$ echo $KDEDIRS


<!--T:12-->
  /usr</syntaxhighlight>
Which may output something along the lines of:
{{Output|1=/usr}}


<!--T:13-->
<!--T:13-->
In this case, your global '''Konversation''' script folder would be <tt>/usr/share/apps/konversation/scripts</tt>. If any of these environment variables contains multiple directories separated by a colon (":"), KDE considers all of them, in the order given.  
In this case, your global '''Konversation''' script folder would be <kbd>/usr/share/apps/konversation/scripts</kbd>. If any of these environment variables contains multiple directories separated by a colon (<code>:</code>), KDE considers all of them in the order given.


<!--T:14-->
<!--T:14-->
The scripts directory in your home folder - <tt>~/.kde/share/apps/konversation/scripts</tt> -, 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.
The scripts directory in your home folder - <kbd>~/.kde/share/apps/konversation/scripts</kbd> - 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 under the home folder for your user account. This way, an update to '''Konversation''' won't overwrite your modifications.


<!--T:15-->
<!--T:15-->
If the above method to retrieve the path of the global scripts folder fails, you can try the output of:
If the above method to retrieve the path of the global scripts folder fails, you can try the output of: <syntaxhighlight lang="shell" inline>kde4-config --install data</syntaxhighlight>
{{Input|1= kde4-config --install data}}


<!--T:16-->
<!--T:16-->
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:
Here are a few more examples of common paths for the global scripts folder in case the above methods to retrieve them are unproductive:
<syntaxhighlight lang="bash">
<syntaxhighlight lang="shell">
/usr/share/apps/konversation/scripts (Gentoo, Kubuntu)
/usr/share/apps/konversation/scripts       # Gentoo, Kubuntu
/usr/share/kde4/apps/konversation/scripts
/usr/share/kde4/apps/konversation/scripts
/opt/kde3/share/apps/konversation/scripts (SUSE)
/opt/kde3/share/apps/konversation/scripts # SUSE
</syntaxhighlight>
</syntaxhighlight>


<!--T:17-->
<!--T:17-->
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):
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): <syntaxhighlight lang="shell" inline>/exec --showpath media</syntaxhighlight>
{{Input|1=/exec --showpath media}}


== How do I make my text bold/italized/underlined? == <!--T:18-->
== How do I make my text bold/italized/underlined? == <!--T:18-->
Line 68: Line 62:
Examples:
Examples:


<!--T:20-->
<!--T:20-->
This is my %Bbold%B text.
* <syntaxhighlight lang="text" inline>This is my %Bbold%B text.</syntaxhighlight>
: This is my '''bold''' text.
*: This is my '''bold''' text.


<!--T:21-->
<!--T:21-->
This is my %Iitalized%I text.
* <syntaxhighlight lang="text" inline>This is my %Iitalized%I text.</syntaxhighlight>
: This is my ''italized'' text.
*: This is my ''italized'' text.


<!--T:22-->
<!--T:22-->
This is my %Uunderlined%U text.
* <syntaxhighlight lang="text" inline>This is my %Uunderlined%U text.</syntaxhighlight>
: This is my <u>underlined</u> text.
*: This is my <u>underlined</u> text.


<!--T:23-->
<!--T:23-->
This is my %Sstruck-out%S text.
* <syntaxhighlight lang="text" inline>This is my %Sstruck-out%S text.</syntaxhighlight>
: This is my <strike>struck-out</strike> text.
*: This is my <strike>struck-out</strike> text.
 
<!--T:34-->
* <syntaxhighlight lang="text" inline>This is my %Mmonospace%M text.</syntaxhighlight> ''(Konversation >= 1.8.22040)''
*: This is my <kbd>monospace</kbd> text.


== Where is the server list? == <!--T:24-->
== Where is the server list? == <!--T:24-->


<!--T:25-->
<!--T:25-->
'''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 [[Special:mylanguage/Konversation/Scripts/Import_mIRC_server_list|this page]] you can find a script that will append the contents of mIRC's venerable servers.ini to your '''Konversation''' config file.
'''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, the [[Special:mylanguage/Konversation/Scripts/Import mIRC server list|Import mIRC server list]] page offers a script that will append the contents of mIRC's venerable servers.ini to your '''Konversation''' config file.


== What is an IRC URL? == <!--T:28-->
== What is an IRC URL? == <!--T:28-->
Line 95: Line 93:


<!--T:30-->
<!--T:30-->
* irc://host:port/%23channel
* <syntaxhighlight lang="text" inline>irc://host:port/%23channel</syntaxhighlight>
* irc://host:port/name,isuser
* <syntaxhighlight lang="text" inline>irc://host:port/name,isuser</syntaxhighlight>


<!--T:31-->
<!--T:31-->
Details: ([http://tools.ietf.org/html/draft-butcher-irc-url-04 expired IETF draft])
Details: [http://tools.ietf.org/html/draft-butcher-irc-url-04 expired IETF draft]


<!--T:32-->
<!--T:32-->

Latest revision as of 00:15, 16 November 2024

Other languages:

I've lost my menubar, how do I get it back?

Pressing Ctrl + M will make it re-appear. It should be noted that most KDE applications follow the standardized shortcut convention, and you should be able to restore your menu to its default assignments this way (most of the time).

My distro turned off the system tray icon, how do I get it back?

SettingsConfigure KonversationBehaviorGeneralEnable System Tray

I have NetworkManager disabled and connect manually, but Konversation fails to auto-connect and needs restarting

Konversation uses the KDE Solid (glossary entry) backend to get network info. To make it reconnect, change the Solid backend to FakeNet.

System SettingsAdvanced tabHardwareNetworkFakeNet, and move it to the top of the list using the arrows.

Apply changes.

Note

Since KDE SC 4.5, this setting is found in the Network Management Backend section of System SettingsHardwareInformation Sources.


Where can I find the scripts included with Konversation (/media, /weather, etc.)?

KDE applications commonly look for their resources in two places, and Konversation is no exception to this. First they search a global directory structure, and then another one called user, 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 values for all scripts shipped with Konversation can be harder to establish, because it depends on how the filesystem your distribution has chosen to implement is laid out.

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

  /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 - 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 under the home folder for 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 the above methods to retrieve them are unproductive:

/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-out text.
  • This is my %Mmonospace%M text. (Konversation >= 1.8.22040)
    This is my monospace text.

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, the Import mIRC server list page offers 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:

  • irc://host:port/%23channel
  • irc://host:port/name,isuser

Details: expired IETF draft