When I restarted XY that manner even though it was closed, the newly established environmental variable does not show up either using your script or in XY's Environmental Variables. I was closing XY normally and then restarting XY using a numpad key I have assigned using AutoHotkey to start XY if not already active. Your script will provide the same information as the XY's Environmental Variables. I was hoping that a way to resolve this issue of using environmental variables throughout the system might be for Don to recognize newly set environmental variables by performing a environmental refresh cid #505 and not require a restart.Įdit : I noticed in the one line of code I had 2 different variables, the use of "set" clears the variable if it already exists, and the setx establishes a new one. Now for some reason it doesn't recognize them at all. It's quite easy to make a local or system environmental variable, but the issue was 2 years ago that XY wouldn't recognize it without a restart. I was curious this morning after seeing TheQwerty's post above so I started experimenting. It's there whether I make a local or system environmental variable, but it's not in XY's listing. Though it's clearly exists in the Control Panel's listing of environmental variables. Temp_files.Code: Select all run "cmd /c /q set MYVAR= & setx MYVAR PizzaMan",0,0 Take a look at what I reported back 2 years ago User Environmental Variable Refresh For some reason now I don't see those in XY's listing of environmental variables. I opened the _broken one in notepad++, ctrl+a then copied the text, and finally pasted it into the window. Here's the two '~ColumnEdit.txt' files if you're interested. Not sure if other vim users would experience this (More likely yes since my configuration is pretty default/vanilla), just thought I'd mention it. If I don't manually delete this line, the rename fails (as you can see by the un-matched icon on the right).Īgain, not a big deal, just something I ran into right off the bat. However, when only renaming 1 file, the new line is there, but it's not being picked up as text (My cursor stops before the blank line instead of on it when I press ctrl+a). This results in no problems (As you can see by the icons). Might be a little hard to see a blank line in screenshots, but here goes!įirstly, when you rename >1 file, there is a blank line at the end (You can see my cursor on it when I press ctrl+a). Not a huge deal, but again not leaving anything behind is the magic of portability. ini.Īlso, deleting the temp '~ColumnEdit.txt' file or keeping it alongside the. This way we could use relative paths (,, etc.) for the editor, instead of hard-coding the path into the. In the spirit of keeping things portable, It'd be neat to move all the configuration into the. Just thought I'd point it out if you ever push a v1.3 and want to suffer through some debugging!Īnyways, thanks a bunch highend, this is a really neat script! It's not that big of a deal, especially since it only applies when renaming 1 file (which I doubt I need my editor to do) and also because I know vim isn't very popular for windows users. This only applies when renaming 1 file, but naming many works fine. Unless I delete that blank line, xyplorer errors out when trying to apply the name change. window, this (normally invisible) EOL character results in a visible and corrupted new line. When the contents of '~ColumnEdit.txt' are pasted into the the Edit Item Names. This script works really well, however I'm having one small issue My editor (Vim via GitBash) applies an invisible EOL (EndofLine) character to every file it saves. Now that I've tried it, I regret not figuring this out years ago!įor anyone reading this, there's a v1.2, which isn't mentioned in the OP. This is awesome! I've always thought it would be nice to edit filenames in my editor, but never got around to writing out a script. Find and select the text editor (that should support a "column edit mode") to use Find and select the "x圜olumnEdit.exe" fileĠ2. This will ask you to find and select two things (and opens a file requester for both):Ġ1. ini file with the same base name as the script after using a "startup wizard". When the script is started for the first time, it creates an. It monitors the "Edit Item Names." window and quits itself, once this window was closed It automatically activates this window (if configured via the. When the file is saved (from inside your text editor), it updates the content of the "Edit Item Names." window xys script to an external text editor of your choice It passes the file that was written by the. The drawback is, it does lack relevant editor capabilities like multiple cursors, search and replace, etc. XYplorer provides "Rename Special - Edit Item Names." which is nice for visually renaming multiple files
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |