dnkl/foot
41
2.0k
Fork
You've already forked foot
243

shell=mtm #904

Closed
opened 2022年01月30日 01:48:17 +01:00 by amy.sh · 2 comments

when the shell=mtm in foot.ini, the prompt starts at the top of the terminal for a split second and then it gets moved down in the terminal. this issue does not occur when you type mtm into the terminal, only when mtm is the shell in foot.ini

attempt to visualize with ascii
```
|
|
|
|
|
|
|~$
|
|
|
|
|
|
```

steps to reproduce: install mtm, set shell in foot.ini to mtm

when the shell=[mtm](https://github.com/deadpixi/mtm) in foot.ini, the prompt starts at the top of the terminal for a split second and then it gets moved down in the terminal. this issue does not occur when you type mtm into the terminal, only when mtm is the shell in foot.ini <details> <summary>attempt to visualize with ascii</summary> ``` | | | | | | |~$ | | | | | | ``` </details> steps to reproduce: install mtm, set shell in foot.ini to mtm
Collaborator
Copy link

The window resize that happens shortly after foot starts (see #453) has been known to trigger some issues before, but I've never seen a case yet where the child program wasn't the likely cause. The window resize can lead to some "flickering" but it shouldn't cause the prompt to be incorrectly positioned (or not printed at all; which is another bug I've seen with mtm).

Some people have mentioned that adding a small delay (e.g. foot sh -c 'sleep 0.1; mtm') usually makes the problem go away.

this issue does not occur when you type mtm into the terminal

Yeah, it's only likely to occur when foot execs a program shortly after being started itself (i.e. with foot mtm or foot -o shell=mtm). If you type a command into an already running shell, the initial window resize already happened long ago.

The window resize that happens shortly after foot starts (see #453) has been known to trigger some issues before, but I've never seen a case yet where the child program wasn't the likely cause. The window resize can lead to some "flickering" but it shouldn't cause the prompt to be incorrectly positioned (or not printed at all; which is another bug I've seen with mtm). Some people have mentioned that adding a small delay (e.g. `foot sh -c 'sleep 0.1; mtm'`) usually makes the problem go away. > this issue does not occur when you type mtm into the terminal Yeah, it's only likely to occur when foot execs a program shortly after being started itself (i.e. with `foot mtm` or `foot -o shell=mtm`). If you type a command into an already running shell, the initial window resize already happened long ago.
Owner
Copy link

Closing as a duplicate of #453

Closing as a duplicate of #453
dnkl 2022年01月30日 14:50:53 +01:00
  • closed this issue
  • added the
    duplicate
    label
Sign in to join this conversation.
No Branch/Tag specified
master
osc-5522
sixel-heap-buffer-overflow
releases/1.27
releases/1.26
releases/1.25
releases/1.24
multi-cursor
releases/1.23
pixman-16f-2
releases/1.22
releases/1.21
releases/1.20
releases/1.19
releases/1.18
releases/1.17
releases/1.16
releases/1.15
releases/1.14
releases/1.13
releases/1.12
releases/1.11
releases/1.10
releases/1.9
releases/1.8
releases/1.7
releases/1.6
releases/1.5
releases/1.4
releases/1.3
releases/1.2
releases/1.1
releases/1.0
1.27.0
1.26.1
1.26.0
1.25.0
1.24.0
1.23.1
1.23.0
1.22.3
1.22.2
1.22.1
1.22.0
1.21.0
1.20.2
1.20.1
1.20.0
1.19.0
1.18.1
1.18.0
1.17.2
1.17.1
1.17.0
1.16.2
1.16.1
1.16.0
1.15.3
1.15.2
1.15.1
1.15.0
1.14.0
1.13.1
1.13.0
1.12.1
1.12.0
1.11.0
1.10.3
1.10.2
1.10.1
1.10.0
1.9.2
1.9.1
1.9.0
1.8.2
1.8.1
1.8.0
1.7.2
1.7.1
1.7.0
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.0
1.2.3
1.2.2
1.2.1
1.2.0
1.1.0
1.0.0
0.9.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dnkl/foot#904
Reference in a new issue
dnkl/foot
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?