<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Search &amp; F3]]></title><description><![CDATA[<p dir="auto">When the Search panel is open, F3 (find next) is not active (it only becomes active when the panel is closed). This obliges to click the button Next, which is much less convenient than using the F3 key. Is it possible to have F3 active while the panel is open?<br />
I would guess (have not tried) that this could apply to other functionalities with the Search panel.</p>
]]></description><link>https://community.notepad-plus-plus.org/topic/15904/search-f3</link><generator>RSS for Node</generator><lastBuildDate>Sat, 18 Apr 2026 13:41:48 GMT</lastBuildDate><atom:link href="https://community.notepad-plus-plus.org/topic/15904.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 09 Jun 2018 07:58:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Search &amp; F3 on Mon, 06 May 2024 10:56:42 GMT]]></title><description><![CDATA[<p dir="auto">Notepad++ 8.6.6 will allow F3 and Shift+F3 to work while the Find or Replace windows have input focus.<br />
See point #6 here: <a href="https://community.notepad-plus-plus.org/topic/25742/notepad-v8-6-6-release-candidate">https://community.notepad-plus-plus.org/topic/25742/notepad-v8-6-6-release-candidate</a></p>
]]></description><link>https://community.notepad-plus-plus.org/post/94668</link><guid isPermaLink="true">https://community.notepad-plus-plus.org/post/94668</guid><dc:creator><![CDATA[Alan Kilborn]]></dc:creator><pubDate>Mon, 06 May 2024 10:56:42 GMT</pubDate></item><item><title><![CDATA[Reply to Search &amp; F3 on Mon, 11 Jun 2018 13:47:05 GMT]]></title><description><![CDATA[<p dir="auto"><a href="https://notepad-plus-plus.org/community/topic/15023/f3-shift-f3-as-aliases-for-find-next-previous-while-find-dialog-is-active" rel="nofollow ugc">Related</a>.</p>
]]></description><link>https://community.notepad-plus-plus.org/post/32934</link><guid isPermaLink="true">https://community.notepad-plus-plus.org/post/32934</guid><dc:creator><![CDATA[Scott Sumner]]></dc:creator><pubDate>Mon, 11 Jun 2018 13:47:05 GMT</pubDate></item><item><title><![CDATA[Reply to Search &amp; F3 on Sat, 09 Jun 2018 10:51:49 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://community.notepad-plus-plus.org/uid/12298">@raananb</a></p>
<p dir="auto">It’s really about where your “input focus” currently is, not really about if the <strong>Find</strong> window is open or closed (but of course closing it shifts input focus to a better place in this case…).  If focus is in the <strong>Find</strong> window, all the usual shortcut keycombos that you are used to while in the <em>editing</em> window are NOT active, so pressing them (e.g. <strong>F3</strong>) does nothing.</p>
<p dir="auto">But all is not lost!  You really don’t have to reach for that mouse! When input focus is with the <strong>Find</strong> window, the <strong>Enter</strong> key does the <strong>Find Next</strong> that you seek.  As a bonus, in recent versions of Notepad++, <strong>Shift+Enter</strong> will do a <strong>Find Next</strong> in the opposite direction.</p>
<p dir="auto">But perhaps you will not like that it is a different keystroke than your brain desires – <strong>Enter</strong> when you think <strong>F3</strong>.  It is (sort of) an issue because it interrupts your workflow to have to remember context in addition to the function you want to execute…a similar necessary brain context-switch was discussed <a href="https://notepad-plus-plus.org/community/topic/15882/search-functionality" rel="nofollow ugc">here</a>–you may be interested in reading that…</p>
]]></description><link>https://community.notepad-plus-plus.org/post/32909</link><guid isPermaLink="true">https://community.notepad-plus-plus.org/post/32909</guid><dc:creator><![CDATA[Scott Sumner]]></dc:creator><pubDate>Sat, 09 Jun 2018 10:51:49 GMT</pubDate></item></channel></rss>