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
{{ message }}
This repository has been archived by the owner on Mar 12, 2023. It is now read-only.
Think it'd be better to add that check the indicators that should fail on multiselection and then instead of erasing the whole message just make those indicators ""?
The text was updated successfully, but these errors were encountered:
This seems to be a difficult issue. What should be shown if I have a template "{line_endings}, Ln {row} Col {col}"? I would say only "{line_endings}" but that's not possible.
the only way I can figure out is add another setting like template_multi_selection. But again, what should happen if I still use "{line_endings}, Ln {row} Col {col}" as template_multi_selection?
I feel there should be multiple set_status with different keys for different situations but I don't have a overview now.
the only way I can figure out is add another setting like template_multi_selection. But again, what should happen if I still use "{line_endings}, Ln {row} Col {col}" as template_multi_selection?
You could ask the user to enter a dictionary of separate segments, e.g.,
"{line_endings}", ← segment 1
", ", ← segment 2 (custom user separator, might need special handling is seg3 is hidden)
"Ln {row} Col {col}"] ← segment 3
And then if the variable inside that segment is invalid/doesn't make sense, simply don't show the whole segment, including the text within it
I feel there should be multiple set_status with different keys for different situations but I don't have a overview now.
Yeah, the indicators could be grouped by window / buffer / caret? And then each group has its own _is_enabled and the rest? Similarly to how you split the update into _update_variables_on_view_activated and _update_variables_on_selection_changed
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Encoding/line ending etc. should still be shown even when there are multiple selections
The last check is the reason
ST-CustomStatusMessage/plugin/listener.py
Line 41 in bcad731
Think it'd be better to add that check the indicators that should fail on multiselection and then instead of erasing the whole message just make those indicators
""
?The text was updated successfully, but these errors were encountered: