summaryrefslogtreecommitdiffstats
path: root/src/buffer.rs
Commit message (Collapse)AuthorAgeFilesLines
* Add backslashes to words with spaces in autocomplete()escsqRory Dudley2024-09-291-1/+11
| | | | | | This patch makes it so that the autcomplete() function automatically inserts the backslash character (`\`) into words with spaces when cylcing through the options.
* Fix Tab/Shift+Tab autocomplete behaviorRory Dudley2024-09-281-32/+57
| | | | | | | | | | | | | | | | | | | | | Previously, switching between Tab and Shift+Tab while cycling through autocomplete options could temporarily mess up the order of items. This patch fixes that flaw by adding two new variables to help keep track of the state: - 'last', the last key that was recorded by getchar(), - and 'length', which keeps track of the length of the last buffer generated by the autocomplete() function. These variables are then checked first whenever the user uses Tab or Shift+Tab. The last know buffer 'length' is used to deal with overflow in the case of Shift+Tab. Finally, the logic for processing the autocomplete directory was moved below the code for handling the actual user input (i.e. appending to the getline() buffer). This is because the last character in the buffer (i.e. the last character the user typed) is important for properly updating the autcomplete working directory.
* Don't panic if autcomplete() failsRory Dudley2024-09-211-45/+4
| | | | | If, for whatever reason, the autocomplete() functions fails, don't panic and quit. Instead, return an empty string.
* Expand filepath autocompleteRory Dudley2024-09-211-15/+134
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch expands upon the last one, by providing a filepath autcomplete routine, which works more similarly to that of zsh or bash. It works for: - Any paths containing the current directory (`.`) - Any paths containing the parent directory (`..`) - Any paths containing the root directory (`/`) - Any paths that don't contain any explicit directory (defaults to the current directory, i.e. `.`) In order to achieve this, the pwd (present working directory) was broken out from the autocomplete() function, and is now recomputed every time a character is typed (in the getline() function). pwd always starts off as the current directory, but may change based off of user input. If the current directory cannot be read (likely due to a permissions issue), dwvsh defaults to the user's home directory for now. The filepath autocomplete also works for paths with mutliple directories now (i.e. /etc/mail/xxx), will still allow you to autocomplete files and directories beginning with 'xxx' inside the '/etc/mail' directory. It is also possible to use the tilda character (`~`) with the filepath autocomplete now (it denotes the user's home directory, for instance, autocomplete works for '~/.config/'). Finally, some logic for Shift+Tab was added to autocomplete. It works the same as Tab, except runs backwards through the files and directories (as opposed to forwards). Notes: Some commented out code was left in this commit, just in case it may have any use in future code (it was quite helpful in figuring out some of the intricaces for proper filepath autocomplete). Speaking of which, the autocomplete code should probably be documented (annotated) a bit better. It is somewhat complex, so it is definitely worth writing some unit tests for (ugh, dangling participle), as well.
* Add autocompleteRory Dudley2024-09-131-16/+161
| | | | | | | This patch adds a fairly rudimentary form of autocomplete. For starters, it only works for filepaths, not for programs. Additionally, it currently only works for the present working directory. You cannot yet autocomplete even one more level deep.
* Slight refactor of getchar() and more handling for getline()Rory Dudley2024-09-011-30/+118
| | | | | | | | | | | | | | | | The getchar() function was changed so that it is able to detect some ANSI escape sequences. To better handle this, getchar() now returns a value from the Key enum, indicating whether or not an escape sequence was found. Currently, the only escape sequences the function deals with are arrow keys. Handling of the left and right arrow keys were added to the getline() function, in order to allow a user to go back and edit their command inplace. Up and down arrow keys are also handled, but they are just ignored for now (i.e. they do not move the cursor around anymore). The local 'pos' variable became an Arc<Mutex<usize>>, since it needs to be reset to 0 if ctrl-c is pressed (the handler for which is outside the scope of getline()).
* Keep track of position in getline()Rory Dudley2024-08-281-0/+10
| | | | | Keep track of the cursor position in getline(), this way it is not possible to backspace the prompt.
* Replace io::stdin().read_line() with custom functionRory Dudley2024-08-241-0/+59
Added the termios crate to facilitate the changing of certain terminal options. It is a wrapper around the termios C library, so 'man 3 termios' for more details. Added the custom getchar() function, with retrieves characters from STDIN as they are typed by the user (as opposed to waiting for a newline, like io::stdin().read_line()). This is necessary, since keys like <tab> and <up> have special functionality, which needs to be acted on before command submission. Added the custom getline() function, which uses getchar() to read characters as they are typed. The getline() function contains the logic for the various key presses. For most characters, we simply push the byte to a buffer, and print it out to the screen (since getline() assumes ECHO is off). Notes: For now, <tab> autocomplete is not finished, so hitting the tab key only replaces the tabs with spaces in the inbut buffer. Also, some edge cases are unhandled in getline(). For instance, using the arrow keys appears to move the cursor keys. The parser gets upset when you move the cursor then try to submit a command, so this needs to be fixed.