Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

System tray feature #18345

Closed
crabdancing opened this issue Oct 28, 2018 · 5 comments
Closed

System tray feature #18345

crabdancing opened this issue Oct 28, 2018 · 5 comments

Comments

@crabdancing
Copy link

Since the previous issue thread (from back in 2015!) on this topic, I will open a new one. #7526

I often need to quickly edit something and then want the editor to quickly go away. On my system, Atom takes an agonizing time to load compared to a C++ compiled app, but it does not take that much system resources while running.

So ideally I'd keep it open but in the background. The problem is that I like to minimize the amount of windows I have open to avoid clutter, so in my workflow, Atom ends up closed most of the time. Which means I never actually end up using it. I will end up reaching for things like Gedit or Xed instead because they open much faster, and anything that eats up precious seconds will be skipped. So, I think a system tray option would vastly improve the usability of this app for my workflow.

Thoughts?

@rsese
Copy link
Contributor

rsese commented Oct 30, 2018

Thanks for reaching out!

Personally, I think it's an interesting idea in relation to startup performance rather than minimizing clutter (though I can see how that could definitely help some people's workflows) - besides the issue you referenced, running Atom in the background has been brought up in other startup performance issues like #3673 for example. So it seems like if startup performance were improved, it sounds like that would somewhat help with the issue you're describing? And there are already issues open about this like #2654 that you can subscribe to if you'd like.

And there has definitely been work around this (e.g. see our performance blog post) and it's something the team thinks about improving where/when they can.

As far as a Windows specific enhancement to in the system tray specifically however, as far as I know Damien's comment still stands today (and as mentioned in the feature request template, we're generally unlikely to work on feature requests any time soon with the work the team has on their plate).


We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.

Thanks for understanding and meeting us half way 😀

@rsese rsese closed this as completed Oct 30, 2018
@crabdancing
Copy link
Author

Hmm. I was under the impression the template was more of a bug submission thing, since it's easy for people to not give enough details in those cases -- but for feature suggestions, details about logs, version numbers, etc, are all pretty much N/A. But if it makes it any easier to process my input, I'll definitely try to stick to the template in the future! Sorry about that.

And yes, improving the startup time would help majorly!

@Ben3eeE
Copy link
Contributor

Ben3eeE commented Oct 30, 2018

but for feature suggestions, details about logs, version numbers, etc, are all pretty much N/A.

There is a specific feature request template that has different questions from the bug report template. When you create a new issue you get a choice between them.

@crabdancing
Copy link
Author

Ah, okies! I'll keep that in mind, thanks. ^.^

@lock
Copy link

lock bot commented Apr 28, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Apr 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants