You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When defining a symbol for the Goto Definition function there is no way to specify that matching symbols should be case insensitive. VHDL (and FORTRAN and others) are case insensitive languages so a lexical object MYOBJECT is fundamentally the same as myobject. More explicitly if I have code such as:
entity foobar is
end entity foobar;
architecture rtl of foobar is
signal MYSIGNAL : std_logic;
begin
MYSIGNAL <= 5;
mysignal <= 4;
end architecture rtl;
with everything scoped correctly, hovering the mouse over MYSIGNAL will correctly reference the definition line above. Hovering over mysignal does not reference any definition even though technically the language would consider these both identical.
The default should remain the same, however I believe the best suggested solution would be to add a flag in the settings key group in the tmPreferences XML file that would instruct Sublime to ignore case when considering matches between objects like:
When defining a symbol for the Goto Definition function there is no way to specify that matching symbols should be case insensitive. VHDL (and FORTRAN and others) are case insensitive languages so a lexical object
MYOBJECT
is fundamentally the same asmyobject
. More explicitly if I have code such as:with everything scoped correctly, hovering the mouse over
MYSIGNAL
will correctly reference the definition line above. Hovering overmysignal
does not reference any definition even though technically the language would consider these both identical.This is discussed here: https://forum.sublimetext.com/t/sublime-text-3-goto-definition-case-sensitivity/12634
The default should remain the same, however I believe the best suggested solution would be to add a flag in the
settings
key group in the tmPreferences XML file that would instruct Sublime to ignore case when considering matches between objects like:The text was updated successfully, but these errors were encountered: