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

Change prompt text cursor position with Left Click fails #635

Closed
Maximus5 opened this issue Jul 31, 2015 · 4 comments
Closed

Change prompt text cursor position with Left Click fails #635

Maximus5 opened this issue Jul 31, 2015 · 4 comments

Comments

@Maximus5
Copy link
Owner

Originally reported on Google Code with ID 635

ConEmu version: 120705

When I tried to position the cursor, it didn't work:

*Steps to reproduction*
1.  Set "Block selection" to "Left Alt" 
2.  Set "Text selection" to "<None>"
3.  Check the "Change prompt (cmd, powershell) text cursor position with Left Click"
option to "<Always>"
4.  Save settings
5.  Type a bunch of text in the console prompt
6.  Try to use the mouse to move the text cursor position
=>  The result will be that you'll switch into selection mode, and will not be able
to position the cursor in the prompt.

The problem is that on the "Mark & Paste" settings there are three option that control
what happens when you left click:
1) "Block Selection" 
2) "Text Selection" 
3) "Change prompt (cmd, pwoershell) text cursor position with Left Click" 

However, these three must use different modifiers or they will conflict, but that's
not obvious from the UI (nor enforced).  That is: you can have one of them set to happen
by default (without a modifier), but the UI will allow you to have two of them set
that way, and if you do, one of the features won't work.  The same is true if you set
two of them to the same modifier.

I love the "position cursor" feature, but the configuration is a bit complicated &
confusing.  Perhaps when that feature is on, it should only work in the prompt line,
and should make it so you can't start selecting text in the prompt line (you can just
start the selection on another line). Personally, I'd be happy to make that trade-off,
and have them both set to no modifier, since I rarely intend to copy what I'm still
typing.

Also, to make the settings cleaner, the three settings should probably all use the
same word (perhaps "<No Modifier>"), where right now the first two "selection" settings
use the word "<None>" where the cursor position uses "<Always>" to mean that no modifier
is necessary.

Reported by jaykul@huddledmasses.org on 2012-07-08 06:44:43

@Maximus5
Copy link
Owner Author

Well. Suppose for a moment, that you need to select _one_ char in the console.
How ConEmu can make choice between two actions (e.g. Text selection & Change prompt)?
My opinion at that moment - it can't.

For clarification.

It is impossible to determine from ConEmu (GUI) side if console is in ReadConsole function.
Moreover, some programs (bash, tcc) do not use this function and process input internally.
So, ConEmu can't rely on "cursor coordinates".

Current style of selection is "cursor inside selection", while in GUI editors is "cursor
outside selection". IMHO, without changing style - combining two actions on one modifier
(or without modifier) is impossible.

Reported by ConEmu.Maximus5 on 2012-07-08 11:42:04


- _Attachment: 2012-07-08_15-38-28.png
![2012-07-08_15-38-28.png](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-635/comment-1/2012-07-08_15-38-28.png)_ - _Attachment: 2012-07-08_15-39-32.png
![2012-07-08_15-39-32.png](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-635/comment-1/2012-07-08_15-39-32.png)_

@Maximus5
Copy link
Owner Author

"<No modifier>" is pretty long. So, "<None>" will be renamed (in text/block) to "<Always>".

Reported by ConEmu.Maximus5 on 2012-07-08 14:29:30

@Maximus5
Copy link
Owner Author

Yeah, I kind of figured you'd say it's not possible to tell when you're clicking in
the prompt (typed text) vs. output text.  In any case, it would be great if there was
a way to force the user to pick different values for those three modifier combos (or
at least make it obvious that they SHOULD).

Reported by jaykul@huddledmasses.org on 2012-07-08 20:51:11

@Maximus5
Copy link
Owner Author

Reported by ConEmu.Maximus5 on 2012-07-10 23:51:46

  • Status changed: Fixed

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

No branches or pull requests

1 participant