Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Can I move cursor by mouse clicking? #239

Open
x10000year opened this issue Oct 26, 2021 · 4 comments
Open

Can I move cursor by mouse clicking? #239

x10000year opened this issue Oct 26, 2021 · 4 comments
Assignees
Labels
feature New feature

Comments

@x10000year
Copy link

xshell supports move cursor to the location of mouse by ctrl+click. can windterm supports the same thing?

@kingToolbox
Copy link
Owner

kingToolbox commented Oct 26, 2021

Yes, I will provide many amazing and exciting new features in the later 2.3 and 2.4 versions. I have been developing basic features for too long, and I don't think I can have fun in development anymore.

Not only move cursor by mouse, but also allows you to use the mouse to select a piece of text and press Del or Backspace to delete it directly, or directly type text to replace it, or even drag and drop it to other editable locations, just like you do in a text editor. This will greatly facilitate the input of commands and texts in terminal.

In addition, Auto completion, Command snippet, Chat bar and Auto wrap after prompt will also be provided. Taking Command snippet as an example, you can add a command snippet:

"gr": "grep -rl $(pattern) "$(dir)"/ | xargs sed -i 's/$(pattern)/$(target)/g'"

then when you want to replace abc with xyz in the folder /home/scripts, you can just type gr in your session and press the tab key and you can get:

grep -rl pattern "dir" | xargs sed -i 's/pattern/target/g'

then type abc to replace the pattern, and press the tab key again:

grep -rl abc "dir" | xargs sed -i 's/abc/target/g'

then type /home/scripts and press the tab key again:

grep -rl abc "/home/scripts" | xargs sed -i 's/abc/target/g'

then type xyz and press the tab key again:

grep -rl abc "/home/scripts" | xargs sed -i 's/abc/xyz/g'

now this command has been completed and you can press the enter key to execute it.

Is this familiar? If you often use this feature in a text editor, you must be familar with it. This time WindTerm will bring this great feature to terminal.

And using Char bar allows you to use the keyboard to quickly operate any number of sessions at the same time, just like twitter, you can use @a ping to send the ping command to the session a, @a, b ping to send the ping command to the session a and b, and #A ping to send the ping command to each session of the session group A.
Even if you operate hundreds of sessions at the same time, you can do it with ease.

Whenever I think of these features, I can't wait. What's more, there are still more than 600 innovative features in total wating to be developed. Most of the features have never been seen from other terminals. This is why I developed WindTerm, not to replace anyone, but to surpass all the existing terminals, including features and performance.

Let me complete the release of 2.2.0 as soon as possible, and then let us enter a new future together. 😄

@kingToolbox kingToolbox self-assigned this Oct 26, 2021
@kingToolbox kingToolbox added the feature New feature label Oct 26, 2021
@MostHated
Copy link

This sounds great.

I am assuming that it would it be possible to have/store a list of commonly used snippets that require no modification that can just be sent as is? Then, with the configuration of the snippets, are they all just available globally, or can it be associated with specific stored connections? Ex. If on Server-A I always need to run commands x,y, and z pretty often, but I use different commands on Server-2, it could have a separate list of commands, but then there is a global one they both can use? Being able to store them and just have them sent to the session, either by a dropdown list, hotkey, completion, select them from a sidebar and double click it to send it to the session "as-is" would be awesome (any of those methods, not necessarily any specific one).

Overall, this sounds like an amazing addition. 👍

@kingToolbox
Copy link
Owner

@MostHated
Yes, if you do not specify any $(...), then the snippet will be sent directly as is.

If you notice, every session has a system attribute, like linux, cmd, powershell and so on. Different systems have their own command snippets. Sessions that use the same system share all command snipptes of that system. Therefore, all Cmd sessions share the Cmd's command snipptes, all Powershell sessions share the Powershell's command snippets. The command snipptes of different systems are independent.

If you want a command snippte to be used for both cmd and powershell, then you can define it as:

{
"snippet" : "...",
"systems" : ["cmd", "powershell"],
...
}

If you want one abc to be used for all systems, then you can define it as:

{
"snippet" : "...",
"systems" : [ "*" ],
...
}

The specific format has not been finalized, but it is probably the case. You are welcome to make any suggestions and we can discuss them together.

@kingToolbox
Copy link
Owner

Hello, I'm glad to have the opportunity to inform you that the feature you want is finally implemented. You can download WindTerm_2.4.0_Prerelease_2 and check it. If there still have any needs, please let me know, thank you.

You can read Free Type Mode to learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

3 participants