Resolve 32/64-bit confusion for Windows editors #780
Conversation
| On a Windows system, if you want to use a different text editor, you must specify the full path to its executable file. | ||
| This can be different depending on how your editor is packaged. | ||
|
|
||
| In the case of Notepad++, a popular programming editor, the application is always shipped as a 32-bit executable. |
There was a problem hiding this comment.
The following is not quite true ...
In the case of Notepad++, a popular programming editor, the application is always shipped as a 32-bit executable.
As I wrote in #733 .....
the state of affairs today, ...., is that a 64-bit Notepad++ is available. .... the 64-bit version doesn't support most plugins. (see https://notepad-plus-plus.org/download/v7.3.2.html)
So in effect, for the immediate future, one should generally continue to only use the 32 bit version.
So I'd suggest something like the following wording:
This can be different depending on whether your editor or Windows version is 32 bit or 64 bit.
In the case of Notepad++, a popular programming editor, you are likely to want to use the 32-bit version (as at the time of writing the 64-bit version doesn't support all the plug-ins ).
Otherwise this rest of the commit looks right.
There was a problem hiding this comment.
Nice, I'll use that. Thanks!
This aims to address the confusion that leads to pull requests like #733, #732, #707, #671, and probably others. It aims to be more explicit with the
core.editorinstructions when it comes to 32-bit editors on a 64-bit system.