Sublime Forum

Hiding pointer (marker)

#1

Hi,

I was able to hide pointer using Ctrl+Shift+A on build 3307, but after upgrading to 3211 I saw that combination does not work anymore. Current keymap shows that: { "keys": ["ctrl+shift+a"], "command": "expand_selection", "args": {"to": "tag"} },

So, how can I hide pointer, what should I write instead of expand_selection?

Thank you.

0 Likes
#2

Can you explain a bit more what “hide the pointer” means in this situation?

The key binding for expanding the selection to the current tag has been the same as you outlined here since Sublime Text build 3006, which is circa 2013, so it seems like whatever issue you’re having isn’t directly related to this key binding changing in core Sublime.

0 Likes
#3

Before 3211, I was able to hide pointer pressing Ctrl+Shift+A. The pointer line is the highlighted line that where the pointer is (blipping thing I mean). Say, if I click 10th line of the code then this line becomes active, right? So if I am not in a file that does not contain any HTML tag such JS PHP or Python, and press Ctrl+Shift+A then the pointer was being invisible and the line unhighlighted. But in HTML files it was selecting the lines to upper direct.

So, I am mostly working with non-HTML files and this key combination was useful for me, because hiding pointer makes me more concentrated to read the code clearly -without something blipping- in the code. Beside selecting multiple areas pressing Alt+Shift+Up or Down arrow, or some other stuff like that and doing delete or something else and just pressing Ctrl+Shift+A to unselect and hide pointer was useful in practicability.

But now, after upgrading, I am not able to hide pointer pressing Ctrl+Shift+A. I wish there would be an option for that something like that;

if press = Ctrl+Shift+A then
  if file = html file then select to upper tag
  else hide pointer and cancel selection etc.

Thank you.

0 Likes
#4

Are you sure you didn’t install a package or a custom key binding of some sort? As mentioned above, this key has always been bound to the same command, so I would think that it should behave the same way now as it did previously.

0 Likes
#5

maybe the command changed to a noop in non-SGML contexts, and you could restore the old behavior with a custom keybinding to remove all selections from the view when not in a HTML or XML file etc.

0 Likes