-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Description
Description of the Issue
When I have autoCompletion\normal.xml defined with function and word, Notepad++ doesn't auto-complete those in Normal Text files (*.txt or *.log) right away. However, if I change the language to something else (like XML and then back to None (Normal Text)), then the auto-completions for Normal Text start working, and any new files opened or created after that
Steps to Reproduce the Issue
- Fresh unzip of portable v8.4.6 and run
Settings > Preferences > Auto-Completion: confirm> From _N_th character=1Enable auto-completion on each input=Function and word completion
- Create new file:
<?xml version="1.0" encoding="UTF-8" ?> <NotepadPlus> <AutoComplete language="Normal"> <Environment ignoreCase="no" /> <KeyWord name="function" func="yes" /> <KeyWord name="word" /> </AutoComplete> </NotepadPlus> - SaveAs
<portableDirectory>\autoCompletion\normal.xml - File > New
- Type
forwand it doesn't suggest anything - Language > XML then Language > None (Normal Text)
- type
fand it suggestsfunction, or typewand it suggestsword- at first I thought the difference between step 5 and step 7 was because normal.xml was new, and the toggle caused it to reload the normal.xml
- from now on, any File > New followed by typing will suggest the words/functions from
normal.xml - File > Close All
- Exit Notepad++ and restart
- type
forwand it doesn't suggest anything- here, it proves that even if normal.xml already exists, Notepad++ doesn't immediately start autocompleting on normal text files
- Language > XML then Language > None (Normal Text)
- type
fand it suggestsfunction, or typewand it suggestsword- but triggering a different language will allow Notepad++ to autocomplete on plain text files
- from now on, any File > New followed by typing will suggest the words/functions from
normal.xml - File > Close All
- Exit Notepad++ and restart
- Language > Perl (so
new 1now shows up as Perl): don't need to type anything - File > New (so now you are editing
new 2which is still a normal text file) - type
fand it suggestsfunction, or typewand it suggestsword- thus, it appears that even triggering a different language through another file will trigger autocompletion on plain text
- File > Close All
- Exit Notepad++ and restart
- File > Open
change.logorLICENSE.txt - Go to the end of and start typing
forw, and it doesn't suggest anything- just loading a normal text file isn't sufficient to trigger autocompletion
- Language > XML then Language > None (Normal Text)
- type
fand it suggestsfunction, or typewand it suggestsword - from now on, any File > New followed by typing will suggest the words/functions from
normal.xml
Expected Behavior
At step 5 or step 11 or step 23, it should suggest function or word as appropriate. It shouldn't matter whether it's the first file loaded in Notepad++ or not, or whether you have changed the language or not: the autocompletions in normal.txt should always apply to normal text files.
Actual Behavior
At step 5 or step 11 or step 23, it suggests nothing, and I have to do a workaround of changing the language away from None (Normal Text) and back, or at least loading or creating a file that uses a different language, in order to get Notepad++ to do autocompletion on normal .txt files.
Debug Information
Notepad++ v8.4.6 (64-bit)
Build time : Sep 25 2022 - 19:51:39
Path : C:\usr\local\apps\npp\npp.8.4.6.portable.x64\notepad++.exe
Command Line :
Admin mode : OFF
Local Conf mode : ON
Cloud Config : OFF
OS Name : Windows 10 Enterprise (64-bit)
OS Version : 20H2
OS Build : 19042.2006
Current ANSI codepage : 1252
Plugins :
mimeTools (2.8)
NppConverter (4.4)
NppExport (0.4)