Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update startup info for Windows 10 #271

Closed
wants to merge 1 commit into from
Closed

Update startup info for Windows 10 #271

wants to merge 1 commit into from

Conversation

MakotoE
Copy link

@MakotoE MakotoE commented Apr 15, 2018

(In section "How do I put my hotkeys and hotstrings into effect automatically every time I start my PC?")
The current instructions do not work for Windows 10. These new instructions also work for earlier versions.

These procedures also work for earlier versions.
@Lexikos
Copy link
Collaborator

Lexikos commented Apr 26, 2018

The old instructions worked on Windows XP. These do not. That's fine.

There are easier ways than what you describe:

  • Run %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup to open the folder.
  • Use FileCreateShortcut %A_ScriptFullPath%, %A_Startup%\%A_ScriptName%.lnk to add the current script to startup. A_Startup should always return the correct location, even on Windows XP and older.

@MakotoE
Copy link
Author

MakotoE commented Apr 26, 2018

I agree that "Run %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup to open the folder." is easier than what I had said, and should be step 2. However, I am not sure about using FileCreateShortcut, since that would involve adding the line into your script and removing it afterwards (or so I presume, I'm not too familiar with AHK yet). Creating the shortcut yourself seems straightforward.

Also does %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup work for Windows XP? If not an additional sentence might be necessary to say this for Windows XP users.

@Lexikos
Copy link
Collaborator

Lexikos commented Apr 28, 2018

Adding a line to a script is an easy thing for an AutoHotkey user to do. One must learn to do this before adding the script to startup becomes useful. Using the variable A_Startup eliminates any concern about OS version or where the folder may be located. It is not necessary to remove FileCreateShortcut after the shortcut is created; only if/when the user wants to run the script without it being added to startup. Another option is to copy the desired script to the clipboard and run FileCreateShortcut %Clipboard%, %A_Startup%\My AutoHotkey script.lnk.

The Start Menu folder is directly under the user's profile folder on XP and older. The original instructions are still the easiest for those versions. Note that "Explore All Users" vs. "Explore" will lead the user to add the script to startup for all users.

Personally, I would never have documented this procedure in the first place. How to add anything to startup is basic power-user/sys-admin knowledge, and instructions can easily be found on various websites with a little searching.

@MakotoE
Copy link
Author

MakotoE commented Apr 29, 2018

I understand, I do think the instructions are vital to the FAQ as I came across the FAQ looking on Google for how to make an AHK script load on login.

I suggest these changes: either move the current instructions (in the main fork) to a sub-section, or remove completely, and add instructions that uses FileCreateShortcut %A_ScriptFullPath%, %A_Startup%\%A_ScriptName%.lnk.

Lexikos added a commit that referenced this pull request May 19, 2018
Supersedes pull request #271
@Lexikos Lexikos closed this May 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants