Refined-github: Please make the extension configurable in Chrome settings

[simonschaufi]

I love this extension but for me it removes a little bit too much. For example the formatting buttons in the editor are gone and also the merge with command line (I need this to test a pull request locally).
I know there are plenty of modifications available but can at least some be configured to be active and inactive?

[hkdobrev]

👍
I wouldn't use this setting, but I see lots of people use the Markdown tools. Here's a review from the Firefox add-on reviews:

This addon make GitHub better.

I still need GitHub markdown tool in comment. It make me faster writing markdown. It should be great if you can bring it back.

Keep up good work. Thank you.

https://addons.mozilla.org/en-US/firefox/addon/refined-github-/reviews/939957/

[busches]

We could extend the safely method to check for configuration now. Would
need a new name, but would centralize the config options.

On Oct 28, 2017 8:17 AM, "Haralan Dobrev" [e-mail] wrote:

👍
I wouldn't use this setting, but I see lots of people use the Markdown
tools. Here's a review from the Firefox add-on reviews:

This addon make GitHub better.

I still need GitHub markdown tool in comment. It make me faster writing
markdown. It should be great if you can bring it back.

Keep up good work. Thank you.

https://addons.mozilla.org/en-US/firefox/addon/refined-
github-/reviews/939957/

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sindresorhus/refined-github/issues/779#issuecomment-340190212,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0WZGHc_yCM47Zfhpj0yE7DByfgmE5cks5swylLgaJpZM4QJ6gT
.

[sindresorhus]

We have more than 9000 users and we've only gotten a couple of requests for bringing back the Markdown toolbar. From all the things we could make configurable, I don't think this is an important thing. It's super simple to learn and use the basics of Markdown by hand. I don't see the point of having buttons to insert #, 1., >, _foo_.

For every option we add, the possible combinations explode, and it increases testing time and possible bugs. We should not add options lightly. It's already a lot of work to maintain this plugin.

[fregante]

It's true that markdown is easy to type, but not always. I doubt you could quote more than one line with this ease or make a numbered list so quickly (which requires strenuously typing 2–3 characters per line)

Bold (cmd+b) and _italic_ (cmd+i) and links (cmd+k) are addable via keyboard but others aren't (lists, quotes). Maybe they could at the very least be implemented as cmd+l and cmd+q 😋 — however without the toolbar these shortcuts would be rather obscure, just like our cmd+u for uploads.

[yakov116]

@bfred-it 100% This is one of the main reasons that I compile the extension myself. I use the lists all the time and code selector.

[fregante]

@yakov116 For fixes like this you can use Stylish to override the extension’s style. I have my own list of unwanted RGH styles that way

[sindresorhus]

@bfred-it That’s a good argument. Maybe we should just bring it back then. I would prefer that over an option. It doesn’t bother me much anyway.

I’m curious what other things you override?

[fregante]

Maybe only these can be hidden since they're easy to add via keyboard:

@sindresorhus Overrides: #566, #637, #610 (although now I _prefer_ hub checkout since it preserves GitHub Desktop's ability to push to forks in one click), and I had more but recently Stylish forgot all of my userstyles 😢

[fregante]

👍 PRs welcome to restore the non-red comment buttons in my screenshot above.

Specific other requests can be searched or made in separate issues.

[gluons]

I also created a simple userstyle to bring it back all. 🙂