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

Menu, intuitive clipboard handling, settings dialog, find - all missing #5064

Closed
Hermholtz opened this issue Mar 21, 2020 · 2 comments
Closed
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Hermholtz
Copy link

Description of the new feature/enhancement

Apart from profile list dropdown there's no menu whatsoever, for example from which I could select "Cut", "Copy", "Paste", "Select all", "Tools/Profiles", "Tools/Options" and more.

Configuring settings by editing JSON is so trendy (after 2010) but rubbish way of configuring software. I'm not opting into learning all possible configuration options. Either enrich default config file with all settings in comment so I can use them without searching the entire internet, or even better provide a dialog to configure it using mouse. It used to be easy to develop in the past, hope it's still like that.

There's no context menu when I select a portion of text and right click. Lame, but ok, for now.

It's not possible (or I can't discover how) to find text in terminal / in the scrollback buffer.

Proposed technical implementation details (optional)

Look at Ubuntu terminal for settings dialog, context menu, features and general look and feel. Look at PuTTY for settings and menu. This thing here is written by 200 people intensely for more than half a year and yay we have tabs! But beyond that it's not too far from cmd.exe...

@Hermholtz Hermholtz added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 21, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 21, 2020
@DHowett-MSFT
Copy link
Contributor

Thanks for the suggestions!

Just a couple notes:

written by 200 people intensely

The core team is four engineers; we're making the best of the absolute onslaught of feature requests we get here on a daily basis, so I'm going to point you to the existing issues for the ones you want. Subscribe to them for updates and click the 👍 button to lodge your support.

In light of that, I'm going to close this out out as a /dupe of #1564 #3789 and #3337.

@ghost
Copy link

ghost commented Mar 21, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Mar 21, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 21, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants