[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r18634 - trunk: doc/source/en/TortoiseSVN/tsvn_dug src/TortoiseProc src/TortoiseProc/LogDialog src/TortoiseProc/Settings

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 18 Feb 2010 17:03:05 +0100

On Wed, Feb 17, 2010 at 23:34, Simon Large
<simon.tortoisesvn_at_googlemail.com> wrote:
> On 17 February 2010 19:52, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>> Author: steveking
>> Date: 2010-02-17 11:52:34-0800
>> New Revision: 18634
>>
>>
>> Log:
>> Introduce new advanced registry entry to disable the Ctrl-Enter feature in various dialogs.
>>
>> +                       <term condition="pot">CtrlReturn</term>
>> +                       <listitem>
>> +                               <para>
>> +                                       In most dialogs in TortoiseSVN, you can use <keycap>Ctrl+Enter</keycap>
>> +                                       to dismiss the dialog as if you clicked on the OK button.
>> +                                       If you don't want this, set this value to <literal>false</literal>.
>> +                               </para>
>> +                       </listitem>
>> +               </varlistentry>
>
> Would it make more sense to call this key CtrlEnter rather than
> CtrlReturn. In the docs and on the mailing list we almost always refer
> to Ctrl+Enter.

You're the doc master, so you decide what's best there :)

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2448805
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-18 17:03:31 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.