Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Console: autocomplete for the command arguments #141

Open
KochynVolodymyr opened this issue Jan 25, 2022 · 5 comments
Open

Console: autocomplete for the command arguments #141

KochynVolodymyr opened this issue Jan 25, 2022 · 5 comments
Assignees

Comments

@KochynVolodymyr
Copy link
Contributor

User wants to have autocomplete for arguments of the command like switches, filenames, dirs or keywords. As an example could be 'git' in the bash.

Currently this issue isn't urgent.

@KochynVolodymyr
Copy link
Contributor Author

@alain-rs TCL itself doesn't have any help for commands arguments. In order to implement this we have to:

  • write some subsystem for command arguments processing
  • fill some map with all arguments for every command.

This will take a while and requires further support.
vivado doesn't have this feature.
Do we need it now?

@alaindargelas
Copy link
Contributor

I think the most important commands that need completion are actually the commands like synth_opts, synth.

Tcl built-in commands or user defined proc arguments can be discovered using the Tcl introspection (info command ....) you can retrieve their arguments and create an argument map db per command at start time as you mentioned, using a tcl script that gets evaluated once. There are examples of such scripts that get invoked by the C++ code and those output gets read back in C++ already in the TclInterpreter.

For the C++ registered commands like synth_opts, synth... we need also to build that mechanism during the registration of the command in the register commands functions.

This is a nice usability feature. Not urgent.

@KochynVolodymyr
Copy link
Contributor Author

I didn't find a way how to retrieve arguments, can you help? info commands... gives only the command name, but not the arguments

@alaindargelas
Copy link
Contributor

@KochynVolodymyr
Copy link
Contributor Author

KochynVolodymyr commented Jun 27, 2022

That works for procedures only, how about commands? standard commands I mean, like source, info,

shivaahir1508 pushed a commit that referenced this issue Jun 15, 2023
* device names

* device names

* device names

* QL/RS options

* QL opations

* plugin settings

* default is no opt

* message

* pin loc converter

* update foedag

* foedag update

* foedag update

* update foedag

* regexp

* update foedag

* default genesis arch

* arch cleanup

* update foedag

* support .vh files

* Update file grouping

* clean option

* project open fix

* log file

* mute option, icon, shell cmd args

* synth,mute options, icon, shell cmds

* update style

* task clear button

* add_library_ext cmd

* Create project update

* per device pnr options

* per device pnr option

* device size in xml

* openfpga pnr options

* no defparams

* help

* litex

* litex wip

* Build type

* suppress check_rr_node warnings

* IP catalog interf with LiteX

* PRODUCTION_BUILD flag

* pin_c support for csv file only

* hash code

* IP generation wip

* About and VPR GUI

* IP Generate wip

* merge about and clean PRs

* typo and IP path

* Device License placeholder

* pinc fix

* ip_catalog command

* ip_catalog command

* License manager for devices

* format

* PRODUCTION_BUILD

* Only check license if there is a target device

* Correct path

* version

* PR view

* typo and incremental sdc

* Icons back

* Remove QML

* Help

* Help

Co-authored-by: Alain Dargelas <alain.dargelas@gmail.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants