Closing due to lack of interest, feel free to re-open if anyone feeling
strongly comes along.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2259#issuecomment-537766585
Closed #2259.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2259#event-2682645008
IMO @codebrainz said it above.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2259#issuecomment-537720973
@b4n, @codebrainz, @elextr: ping. What's the final decission? Merge or close it
unmerged? I'm fine with both, just want to get the ticket done.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Isn't there some kind of Geany "user resources" forum / wiki where users upload
filedefs, templates, ctags etc? I think this would fit well there. This doesn't
add any bloat (as per my understanding what this discussion is about^^) to
Geany.
--
You are receiving this because you are
If nobody except @franco999 in 2015, including this pull requestor, is
convinced this is useful, then I guess it should be closed?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I still don't have a strong opinion, but as is the file doesn't seem very
useful.
I tend to agree with @codebrainz, mostly because in 2019 it's likely user CSS
will add rules on top of a framework, and if it's not it's likely be to either
highly complex or very simple.
If we suppose very
Yeah, I don't feel strong on this one either. In the original post it seemed to
be reasonable for some people. The original PR is already 4 years old and the
original source branch seems to have been removed. Let's close #607 by merging
this one or let's close both if it's not going to be
Looks ok. I doubt it will ever get used, but has minimal cost to add.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2259#issuecomment-521036457
This PR adds a "new file" template for CSS files. It's meant to be a
follow-up/replacement for PR #607.
Following the discussion there the template includes the ```{fileheader}```
token and only minimal CSS content without much placeholders bloating up the
file.
IMHO we cannot predict much
10 matches
Mail list logo
