* Expose RuneBuffer.Set through Operation's API
This allows a user to prefill a line before the user is given a prompt,
so that you can provide a default, user-editable input line.
* Add a Instance.ReadlineWithDefault API method
This will pre-fill the Operation.RuneBuffer with text before prompting
the user, and provide her with a method to edit the provided default.
* Add support for solaris
* Change state to handle system dependent termios type.
* Move syscalls to get and set termios to functions in files only built
for respective platforms.
* Create `term_unix.go` go file built on all supported unices except
solaris with types and functions valid for all of them.
* Change `MakeRaw` to set VMIN and VTIME to default values.
Fixes#95.
* Fix error handling
Doing the string comparison could be improved, but at least we should
return an error, if it is not "errno 0".
usql is a new project that is making extensive use of readline. usql is
roughly 3 days old, and already has over 1100 stars. This change adds
usql to the README.md and reorders projects listed in the "Repos using
readline" section.
The calculation to determine how many spaces to use when padding
columns wasn't taking into account the length of the 'same' portion of
the completions and was only using the length of the completion
itself. This frequently caused the printed completions to wrap, making
the completion list much harder to read.
It is possible for `opHistory.Rewrite` to be called from
`opHistory.historyUpdatePath`. This is problematic, because both methods
grab a lock, and Mutexes in go are not reentrant. This change pulls out
the logic in Rewrite into `opHistory.rewriteLocked`, and retains the
public facing method.
I updated the switch in vim.go to treat 'w' and 'W' differently to 'e' and 'E'.
I then added a method to runebuf.go to provide the logic for that motion.
tested and working.
* Dynamic autocompletion implemented
Now there is a new item type "PcItemDynamic" which takes function as
parameter.
When it comes to autocomplete at this position, the function is called,
the whole line is given to it (for example if autocompletion depend on
previous autocompleted field) and functio should return possible strings
how to continue.
Example usage:
* listing some dynamic key-value storage
* listing files in directory
* Dynamic autocompletion: Updated example
* Dynamic autocompletion: Internal Do() is passing the original full line
To serve it to dynamic autocompletion functions. Previously passed line
was only following segment (which doesn't work).
* Dynamic autocompletion: New dynamic interface added + type assertion in Do function
Do function was split into doInternal with changed declaration and Do
with original declaration.
* Add ClearScreen operation on Ctrl+L
* Remove TODO from clear screen in readme
* Don't use external command for ClearScreen
* Remove duplicate ClearScreen function
Paul Tagliamonte