-
Notifications
You must be signed in to change notification settings - Fork 0
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
Mourning for the Brackets #14860
Comments
F |
F |
F |
F |
F |
F |
F |
F |
The same here! F |
F |
F |
Hi :-) Let's organise! |
|
You can keep me in too... |
What's brackets-cont? |
Also may I suggest a name? |
I'll vouch for |
find and replace?
Feels weird to me. |
It is still a lot of files to cover. It requires us to change almost every file. I think that we need to work on features that are of some value to the users rather than changing the name in the source code.
Yes, agreed. Let's keep it |
|
hi :-)
|
Hey! Can you please make a killedByAdobe? They wear most of their vile acts with pride
I fear for the Substance suite that was recently acquired by them. PS: I own killedbyadobe.com and can transfer/redirect the domain for free. |
Friday Apr 16, 2021 at 20:24 GMT
Originally opened as adobe/brackets#15342
Deposit your "F" here.
![See you again, Brackets, my big friend!](https://camo.githubusercontent.com/46bc8eed860f50dca8aa83656aa03be337f47d455195bf19e7ba53d55b224463/68747470733a2f2f6d656469612e67697068792e636f6d2f6d656469612f6b68743569614e336e396d726d2f67697068792e676966)
In memory of Brackets (2014-2021)
The text was updated successfully, but these errors were encountered: