Bug 144232 - Please document how to avoid Auto Replace
Summary: Please document how to avoid Auto Replace
Status: VERIFIED FIXED
Alias: None
Product: konversation
Classification: Applications
Component: documentation (show other bugs)
Version: 1.0.1
Platform: Debian stable Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-15 00:47 UTC by Philippe Cloutier
Modified: 2011-11-14 05:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Cloutier 2007-04-15 00:47:46 UTC
Version:           1.0.1 (using KDE KDE 3.5.5)
Installed from:    Debian stable Packages
OS:                Linux

I was trying to tell someone to type "dbug:######" in Run Command to see a bug report, but that went out as
<chealer> kokoko1: type "dhttp://bugs.kde.org/show_bug.cgi?id=402185" in Run Command

I couldn't find how to avoid Auto Replace until I asked on #konversation where Sho_ learned me I could use Ctrl+Return to avoid parsing. I asked him whether this was documented and he replied "probably not".
Please document this tip.
Comment 1 Burkhard Lück 2011-07-20 20:09:30 UTC
<qandaentry>
<question>
<para>How to avoid the <guilabel>Auto Replace</guilabel> feature of the <interface>Input Line</interface>?</para>
<title>The &konversation; Handbook</title>
<date>2010-10-14</date>
<releaseinfo>1.3</releaseinfo>
</question>
<answer><para>Use <keycombo action="simul">&Ctrl;&Enter;</keycombo> instead of just &Enter; to avoid parsing and 
automatically replacing the text in the <interface>Input Line</interface> according to the options in the settings 
dialog page <menuchoice><guimenu>Behavior</guimenu> <guimenuitem>Auto Replace</guimenuitem></menuchoice>.
</para></answer>
</qandaentry>
Added some time ago.
Comment 2 Philippe Cloutier 2011-11-13 21:19:07 UTC
Thanks, verified in 1.4 beta.
Comment 3 Eike Hein 2011-11-14 05:04:56 UTC
Thanks for the follow-up!