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
Jline3 provides expander functionality which is turned off in sqlline since beginning... (I guess the reason is that in case of default behaviour it expands if input word starts with an exclamation mark, like commands in sqlline)
The original idea of it is following [1].
At the same time Expander interface can expand something based on input word and history and something input word based only which are not started with !. It allows to introduce live templates like for instance in most IDEs.
The idea is
provide functionality of live templates based on Jline3's expander functionality
provide a list of built-in live templates (currently I think about simple property file)
provide functionality to add new live templates via e.g. new specific commands
live templates expansion should have lowest priority i.e. if anybody defines live templates the same as an existed command or keyword then completion will be done rather than live template expansion
I'm glad that it's possible, but I don't think that it's very useful. I don't think I'd use it, personally. Maybe I expect less from a shell than I expect from an IDE. :)
Jline3 provides expander functionality which is turned off in sqlline since beginning... (I guess the reason is that in case of default behaviour it expands if input word starts with an exclamation mark, like commands in sqlline)
The original idea of it is following [1].
At the same time
Expander
interface can expand something based on input word and history and something input word based only which are not started with!
. It allows to introduce live templates like for instance in most IDEs.The idea is
here it is an implemented live template for
ctas
which will be expanded intocreate table as select
after hitting tab 4ae059b[1] https://www.gnu.org/software/bash/manual/html_node/Event-Designators.html
The text was updated successfully, but these errors were encountered: