| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The word “highbright” was spelled as “hightbright” in a few places.
|
|
|
|
|
|
This will fall back to Tramp's shell if the login shell cannot
be determined.
|
|
Lets the user specify a shell for all Tramp methods.
|
|
Lets the user specify 'login-shell as a SHELL in
`vterm-tramp-shells', which leads to vterm starting with the
remote location's login shell.
|
|
Set the truncation slot for 'buffer-display-table' to the ASCII code for
a space character (32) to make the vterm buffer display a space instead
of the default truncation character ($) when a line is truncated.
|
|
- When checking for vterm-mode, also support modes derived from vterm
|
|
When use [lf](https://github.com/gokcehan/lf) to list files, emacs-libvterm may
read partial multi-byte character, for example:
$ echo -n '招聘' | hexdump -C
00000000 e6 8b 9b e8 81 98
; get "招", control sequence and partial character
(vterm--filter process "\xE6\x8B\x9B\e[14;111H\xE8")
; now full "聘"
(vterm--filter process "\x81\x98")
This will send "\xE8" to libvterm which is not a full character.
|
|
|
|
Allow using different background and foreground colors for same ANSI
index, analogously to how term-mode does it.
Remove magical indices for underlined cells with default foreground and
inverse-video cells with default background. Instead, pass relevant
info to lisp function to handle these cases at higher level.
* elisp.c, elisp.h (Fapply): New binding.
(vterm_get_color): Add new argument for optional attributes.
* vterm-module.c (cell_rgb_color): Pass relevant attributes to
vterm_get_color.
* vterm.el (vterm--get-color): Use foreground or background color of the
face depending on received attributes.
* README.md: Update documentation
|
|
* vterm.el (vterm-color-bright-*, vterm-color-palette): New faces.
(vterm--get-color): Use new bright faces.
* README.md: Mention new faces.
|
|
Without this patch, I am able to click somewhere below the last
prompt line and move the cursor there. I don't think this was an
intended feature, it feels more like a weird quirk.
We don't have any function telling us the point or line number of the
last prompt, and it doesn't seem to be easy to implement, so I
needed to workaround this.
|
|
I didn't find an easy way to determine whether the cursor is in the
last prompt line or what the prompt line number even is. And one
cannot assume the prompt line is the last line of the buffer beacuse
vterm is basically a rectangle filling the whole buffer. As a
consequence `(line-number-at-pos (point-max))` _doesn't work_
because `(point-max)` _doesn't work_.
With this patch, it is possible to find the prompt line using:
(line-number-at-pos (vterm--get-beginning-of-line
(vterm--get-cursor-point)))))
And in case the command in prompt is long and wraps into multiple
lines, its end can be found using:
(line-number-at-pos (vterm--get-end-of-line
(vterm--get-cursor-point)))))
|
|
When the buffer is empty,
(get-text-property (1- (point)) 'vterm-line-wrap)
throws an error.
This situation happens when the empty string is passed as argument to
`vterm--filter-buffer-substring`.
|
|
when vterm-copy-mode-remove-fake-newlines is not nil.
See #497 .
|
|
If emacs-vterm is started on a remote, use the same shell as TRAMP. That
will guarantee that the shell exists on the remote.
A shell could be chosen using `vterm-tramp-shells', but it tied to a
specific TRAMP method. However, the same method (ssh) could be used to
connected to different remotes, each with different default shell. So,
we could use TRAMP to get the shell on per-remote basis.
|
|
The environment of each project may be different, and "dir_locals.el" provides
an excellent way to configure each project separately. This patch enables config
project environment by using "vterm-environment."
|
|
|
|
from vterm--self-insert
|
|
|
|
It should be boolean
|
|
|
|
and vterm-send-{up/down/left/right/prior/next/meta-dot/meta-comma/ctrl-slash}.
and would be removed in v0.1
|
|
|
|
|
|
|
|
|
|
try fix #598. treat `ESC =` as control seq.
|
|
|
|
|
|
|
|
|
|
rewrite these functions with vterm--translate-event-to-args.
|
|
see https://invisible-island.net/xterm/ctlseqs/ctlseqs.html for `ESC =`
when run ghci it echo "\e=Prelude>",
I think `\e=` should be treat as control seq?
|
|
Declare variable before first use
|
|
|
|
|
|
|
|
|
|
In truth `looking-back' does not (yet) require the second argument,
but since 5161c9ca6a6107da30d411fb2ad72e01d08e5704 it claims that
it does.
Instead of merely silencing this warning it would be better to
provide a non-nil value for LIMIT. The reason that this function
is now advertised as requiring two arguments is that it may perform
horribly if no proper limit is specified.
|
|
Read next input event and send it to the libvterm.
This is useful for controlling an emacs session within emacs-libvterm.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
