# Where is the COMPLETE list of up to date Keyboard shortcuts? and Emmet not working
**URL:** https://forum.pinegrow.com/t/where-is-the-complete-list-of-up-to-date-keyboard-shortcuts-and-emmet-not-working/11454
**Category:** Bug Reports
**Created:** [February 25, 2026, 11:56pm UTC](https://forum.pinegrow.com/t/where-is-the-complete-list-of-up-to-date-keyboard-shortcuts-and-emmet-not-working/11454 "2026-02-25T23:56:30Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@schpengle](https://forum.pinegrow.com/u/schpengle)
#### Post date: [February 25, 2026, 11:56pm UTC](https://forum.pinegrow.com/t/where-is-the-complete-list-of-up-to-date-keyboard-shortcuts-and-emmet-not-working/11454/1 "2026-02-25T23:56:30Z")
Hi , where is an UP TO DATE, COMPLETE list of the PG shortcuts?
I can see this one in the docs,
> **[Keyboard Shortcuts | Pinegrow Web Editor](https://pinegrow.com/docs/master-pinegrow/keyboard-shortcuts/)**
>
> Pinegrow has many useful keyboard shortcuts that can make your work even faster.
which is the same as the one for PG V4, here
> **[Keyboard Shortcuts | Pinegrow Web Editor](https://docs.pinegrow.com/docs/master-pinegrow/keyboard-shortcuts/)**
>
> Pinegrow has many useful keyboard shortcuts that can make your work even faster.
but DOESN’T
Contain the ones for commenting out code/blocks of code, mentioned here,
> [@Comment out Codeeditor](https://forum.pinegrow.com/t/comment-out-codeeditor/7217):
>
> How can I comment out elements in Pinegrow Code Editor. I have already searched and activated everything. In the forum was also the CMD +/ but that does not work. I work on a MAC. Maybe someone here can give me a tip.
or the one for the PG program Panes views, here (and would these still work with the new PG9 UI? )
> [@Shortkeys & Productivity](https://forum.pinegrow.com/t/shortkeys-productivity/8298/3):
>
> Hey Plunky, Thanks for your comment! The CTRL - Z does not seem to work for me to delete the last class of a selected element. Streamlining your workflow by minimizing mouse usage often leads to increased efficiency in creation. Employing a quick keyboard shortcut and promptly typing the desired element for selection generally proves to be considerably faster than navigating through an extensive menu by clicking and hovering. I’ve witnessed proficient video editors who masterfully harness key…
Specifically
> [@Shortkeys & Productivity](https://forum.pinegrow.com/t/shortkeys-productivity/8298/4):
>
> Hi wave I normally use: . CTRL + L to access the class panel. It scan and brings up the classes i use thee most . CTRL + D Obvious… . CTRL+ H It brings out the code panel, focused on the element I’ve selected . CTRL + G Grid I agree that having a simple personal set of shortcuts could come handy - within AI / PS / INDD i setted up all sort of strange shortcuts for my needs, so I understand you. Anyway, I see it’s from August your post, how’s it going with Pinegrow? Hope you enjoy i…
There are also other ones that I vaguely remember, like
Selecting code in code view
and
OPT/ALT + Click
To view the corresponding element/structure in the Page view.
I cant find that anywhere.
And
Then there are sneak ones like this
> [@Editor Auto complete option](https://forum.pinegrow.com/t/editor-auto-complete-option/3484/5):
>
> What you theoretically could do is to disable auto-complete in the Pinegrow settings (support -\> settings -\> Code editing) and use CTRL + space in case you want it on the fly. I haven’t tried it out, though. Cheers Thomas
Also while using FIND shortcuts,
I note that they bring up different controls based on whether you are in the page view
Or code view.
IN the code view, I found that the controls, CMD and G etc didnt work to find next element,
Just nothing happened, crickets….
BUT
Then, after clicking Page view.. and using the CMD and find there, I got. different search window.
however, when I tried CMD +G there…. it opened up the CSS Grid panel instead.
As stated here,
> [@Keyboard shortcut for Repeat Search does not work](https://forum.pinegrow.com/t/keyboard-shortcut-for-repeat-search-does-not-work/3038):
>
> According to the Pinegrow Help (Support | Keyboard shortcuts), you can search in the code editor using keyboard shortcuts: CMD-F for Search, CMD-G for Find next. But in fact CMD-G opens a “CSS Grid” popup window. Is there any way to configure this behaviour? I’m working on Windows 7 64bit with Pinegrow 5.41 PRO Personal.
HOWEVER,
Once that window opened, then the grid panel, i closed both, now, once I returned to the code view… CMD +G did indeed, now work to highlight the next instance of the item in the search box after the code view CMD+F.
And IM trying to find out if there are ones for VSCode and PG when using together.
I seem to remember there was…. To do something in VSCode that affected PG and vice versa.
SO, where is an all encompassing truly complete list of all the PG shortcuts plus all the other unknown ones.
AND it might be a good idea to then update the incomplete PG docs listed above.
and… while trying out the shortcuts,
I found that yet again, Emmet shortcuts, still don’t work ☹
as stated here
> [@Emmet not working](https://forum.pinegrow.com/t/emmet-not-working/7746):
>
> Hi guys, don’t know if its a bug or me, but all suddenly emmet doesn’t work in code editor, even if i have the option checked in Support / Settings/Code Editing [immagine] Am i missing something?
and here
> [@Pinegrow Settings → Use Emmet in code editor. Some hotkeys don't works](https://forum.pinegrow.com/t/pinegrow-settings-use-emmet-in-code-editor-some-hotkeys-dont-works/195):
>
> These hotkeys are not working: Cmd-L: Select line Cmd-Shift-M: Merge Lines Cmd-B: Reflect CSS Value (interfere with Pinegrow) How to fix it? How to redefine Pinegrow’s hotkeys?
So ive spent hours now, trying to get shortcuts to work, trying to get emmet to work, scouring docs, forums, and still not got them to work.
Written no code……
---
### Author:  [@schpengle](https://forum.pinegrow.com/u/schpengle)
#### Post date: [February 28, 2026, 7:26pm UTC](https://forum.pinegrow.com/t/where-is-the-complete-list-of-up-to-date-keyboard-shortcuts-and-emmet-not-working/11454/2 "2026-02-28T19:26:06Z")
SO does anyone have a complete list of shortcuts?
Or more spurious, randomly discovered ones?
Cheers
---
### Author:  [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)
#### Post date: [February 28, 2026, 7:37pm UTC](https://forum.pinegrow.com/t/where-is-the-complete-list-of-up-to-date-keyboard-shortcuts-and-emmet-not-working/11454/3 "2026-02-28T19:37:15Z")
The “official” list is the one that’s here.
Soon (no ETA) we’ll run a verification/validation to see which ones are missing and which might have been changed without the list being updated.
---
### Author:  [@schpengle](https://forum.pinegrow.com/u/schpengle)
#### Post date: [February 28, 2026, 9:39pm UTC](https://forum.pinegrow.com/t/where-is-the-complete-list-of-up-to-date-keyboard-shortcuts-and-emmet-not-working/11454/4 "2026-02-28T21:39:01Z")
Cheers for that, I knew Id seen some more somewhere. SO I was going through all the menu drop downs collecting them from various drop down menus - until I found this one too .
Also, CMD+W on mac, to close a file actually closes the entire program, not just a file open in PG, it behaves as CMD+Q on Mac.
EXCEPT that ,
CMD+Q - the official Mac shortcut to quit and app, will cause a
\*Do you want to leave? changes may not be saved” pop up to display,
-even when everything is saved.
Whereas, CMD+W will just instantly quit, if no changes or, if there HAVE been changes, create the
” **Unsaved changes**
One or more pages or component libraries (see File → Manage libraries and plugins) have unsaved changes. Are you sure you want to quit the app?
Pop up to appear.
ALSO,
If you right click the Upper Left Pinegrow Icon, and select
”Reload App\*
It will pop up a
**changes may not be saved**
Pop up,
so you select the CANCEL button,
well,
it STILL reloads the App anyway.
Except it doesnt actually reload the original instance, it creates a new one.
So I know have TWO instances of Pinegrow 🙂
How handy!
And now CMD+W will close the most recently opened instance of Pinegrow.
This confused me for a a bit.