That way, I have much quicker access to them in the heat of a fight and don’t have to worry about missing the F1-F4 keys. Fortnite Battle Royale settings for Consoles If you’re a console player, there are a few different presets you can use for either the PS4 or Xbox One controller.

Try this bit of code: (mapc (lambda(x) (global-set-key x 'auto-name-macro)) '([f5] [f6] [f7] [f8])) (defun auto-name-macro (arg) (interactive 'p') (if defining-kbd-macro (progn (kmacro-end-or-call-macro arg) (fset (intern (format 'mcr-%s' last-command-event)) last-kbd-macro)) (execute-kbd-macro (intern (format 'mcr-%s' last-command-event))))) You start macro definitions with f3 as before, but now f5, f6, f7 and f8 function in the same way as f4, except each remembers their own macro. You finish definition with the key and then call it again with the same key. Exactly like f4. Macros also get names, e.g. Mcr-f5, mcr-f6., so you can call them with M-x instead.

UPD: macros can reference each-other and be bound to any key There's more than a few lines of code so I've put it at. The setup is just (require 'centimacro) f5 will call centi-assign. • It prompts you where you'd like your next binding to be, so you press f6, for instance. • The macro is now recording, and pressing f6 will stop it and assign the new macro to f6.

In Outlook 2016 for Mac, it is not feasible to directly add a Google calendar. However, if you are using an Exchange account or Office 365 for Business account, you can firstly add the Google calendar from OWA (Outlook Web App) and then Google calendar will automatically sync to Outlook for Mac. Here are the steps: 1. Outlook 2016 for Mac users who are part of the Office Insider Fast program will be the first to try this new feature. To become an Insider, simply open up Outlook, click Help > Check for Updates and then follow the directions found here. Not all Insiders will see the new Google Account experience right away. Microsoft has added Google Calendar and Contacts support to Outlook 2016 for macOS, as well as fixing several serious security flaws.

• Now you can use what you defined in f6 for other macro, say f7, but it could be C-e, it's not restricted to functional keys. Here's an example: foo;; Now inserts 'foo'. Bar;; Now inserts 'foobar'.

--;; Now inserts 'foo-foobar-foo'. Omg;; Now inserts 'omg',;; - 'omgbar',;; - 'omgbar-omg-omg'. Well assigning a macro to a key is trivial. Just record it as usual, then type: C-x C-k b I'd also suggest that you don't want to waste 12 useful bindings on 'record a macro' when one (pre-existing) binding will do, so you may prefer to adapt to this approach rather than pursuing the original request. Lastly, note that F5- F9 are all reserved for the end user, but other function keys are not, and already have useful bindings (including keys for recording keyboard macros, funnily enough), so I would focus on those. (If you're running out, you can always make one or more of them a prefix binding.).

I don't think that you can do this exctly as you specified, because any function you write to help with this has to have (start-kbd-macro) as the last call in it - that's the way that start-kbd-macro works. Format hard drive for both mac and pc. This prevents it from naming the keyboard macro after the user finishes recording it. The only way I can see to make something similar would be to have shift-F1 be the key that you use after you finish recording the macro that is to be stored in F1.

The user would have to start recording a kbd macro the usual way, but hit shift F1 after he completes it. You could then easily put a function on shift-F1 that renames the macro to the function that you have bound to F1. The code would be something like this: (defun assign-macro-to-f1 () (interactive) (name-last-kbd-macro 'f1-kbd-macro) (global-set-key[(f1)] (execute-kbd-macro `f1-kbd-macro)) ) (global-set-key [(shift f1)] `assign-macro-to-f1) (note - I tried also ending the kbd macro in the shift-f1 function, but it seems like messing around with kbd macros in functions is problematic. Better to let them record the macro the normal way, and save it with this function). Here is a solution I have used: After recording the macro, name it using C-x C-k n. Then you can use M-x insert-kbd-macro and give it the name of the macro you just defined. That will insert some lisp code which defines the macro.