search

brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

[CLOSED] Files beginning with a dot (hidden files) #6153

Open core-ai-bot opened 2 years ago

core-ai-bot commented 2 years ago

Issue by say2joe Thursday Feb 06, 2014 at 22:01 GMT Originally opened as https://github.com/adobe/brackets/issues/6781

I don't know why in the world someone decided it was a good idea to create an IDE which hides files, but it is absolutely stupid. If I'm writing code (not a word processor), why would I want files hidden???

Enable the sidebar to view ALL files. What an annoying oversight -- we're writing code and need access to files beginning with a dot. If I want to use Finder, I'll use the OS -- not an IDE.

You can always have an option in the View menu to hide (or show) them! By default, these files should never be hidden... I can't even begin to express how incredibly annoying this is.

core-ai-bot commented 2 years ago

Comment by njx Thursday Feb 06, 2014 at 22:08 GMT

Well, sounds like you can just assume we're stupid then. Case closed :)

But seriously...

Brackets isn't at 1.0 yet, and there are a number of features that aren't finished yet. In particular, one of our upcoming user stories is about making exclusions from the file tree and other features configurable. For now, since we don't have that infrastructure yet, we needed a way to get rid of things that are commonly hidden in dot-folders (like .git) that would gum up things like file indexing. We thought that was a reasonable tradeoff in the interim in order to make it so that our features wouldn't screw up in the presence of source control metadata, etc.

Closing as "move to backlog" since making exclusions configurable is already on our roadmap. Thanks for your feedback!

core-ai-bot commented 2 years ago

Comment by peterflynn Thursday Feb 06, 2014 at 22:40 GMT

Btw, if you're running from source you could edit _exclusionListRegEx in ProjectManager.js to manually customize this for now. Bear in mind there will be a performance hit if you stop filtering large subtrees like the .git folder; but exposing individual files like .gitattributes should be fine.

core-ai-bot commented 2 years ago

Comment by say2joe Thursday Feb 06, 2014 at 23:51 GMT

Ah, how the irony thickens... I was actually trying to easily edit my .gitignore file at the time. At any rate, I love the IDE (and recently introduced the FED team at Acquity Group to it), effort and please don't confuse my statement of a "stupid" oversight to an inference that the developers / team are stupid people. I would never make such a proclamation.

On another note, Peter Flynn has offered a suggestion on how I might make things work best for my development efforts.

core-ai-bot commented 2 years ago

Comment by njx Thursday Feb 06, 2014 at 23:55 GMT

It is also true that we could just stop blacklisting .gitignore. I'll reopen this to see if we'd want to take that.

core-ai-bot commented 2 years ago

Comment by say2joe Friday Feb 07, 2014 at 00:01 GMT

Thanks ... and sorry for the initial "stink" I made. I had done some searching on using Brackets from the CLI, but it looked difficult. Apparently, the stuff indexed by Google (or conversations in general on this topic) are antiquated. I was easily able to simply create an alias (alias brackets='open -a Brackets.app') and open the file in my currently open editor instance (mymac:workingdir user$ brackets .gitignore). Guess the CLI issues have all been resolved.

core-ai-bot commented 2 years ago

Comment by ghost Saturday Feb 08, 2014 at 21:38 GMT

If you want to see hidden files, why did you hide them?

core-ai-bot commented 2 years ago

Comment by MiguelCastillo Saturday Feb 08, 2014 at 22:01 GMT

@say2joe Chill dude. Maybe I am mistaken, but I am sure you could have come up with much better ways to articulate your message. Your approach puts people off.

@njx It would be nice to make this configurable, so I am glad this is in the current road map ;)

core-ai-bot commented 2 years ago

Comment by njx Monday Feb 10, 2014 at 19:19 GMT

Marking medium priority, starter bug. Making this configurable is on the roadmap, but let's do a short-term fix for this specific issue by removing .gitignore, .gitattributes, .cvsignore, and .hgignore from the regexp in ProjectManager.js.

core-ai-bot commented 2 years ago

Comment by TVScoundrel Tuesday Feb 11, 2014 at 06:48 GMT

Almost seems too easy, but I had to start somewhere and fix my first bug. Created a pull request #6833

core-ai-bot commented 2 years ago

Comment by say2joe Tuesday Feb 11, 2014 at 20:41 GMT

You guys are great... I hope to contribute in the near future. I need to get into the source code / JavaScript first a bit more (I have, however, run the setup_hack shell script).

Joe Johnson 657-464-HTML

On Mon, Feb 10, 2014 at 10:49 PM, Tom Van Schoor notifications@github.comwrote:

Almost seems too easy, but I had tostart somewhere and fix my first bug. Created a pull request #6833 https://github.com/adobe/brackets/pull/6833

— Reply to this email directly or view it on GitHubhttps://github.com/adobe/brackets/issues/6781#issuecomment-34730181 .

core-ai-bot commented 2 years ago

Comment by lkcampbell Tuesday Feb 11, 2014 at 23:16 GMT

@say2joe, fix merged. You should now be able to see .gitignore, .gitattributes, .cvsignore, and .hgignore all of the time.

FBNC to you to test in Dev build or Sprint 37.

core-ai-bot commented 2 years ago

Comment by say2joe Wednesday Feb 12, 2014 at 00:49 GMT

I'd be happy to test ... but, I'm unfamiliar with FBNC?

core-ai-bot commented 2 years ago

Comment by lkcampbell Wednesday Feb 12, 2014 at 02:32 GMT

Fixed but not closed.

core-ai-bot commented 2 years ago

Comment by njx Wednesday Feb 12, 2014 at 03:47 GMT

@lkcampbell For bugs filed by non-committers, we generally just test it ourselves and then close it if we think it's fixed - the filer can reopen if they get the next release and find that it's still broken.

Closing as fixed -@say2joe let us know if you still see it in the next release.