This is probably quite a simple oversight on my part, but googling hasn't helped, so...
The file browser always appears empty in my installation of Textmate 2.
I thought it might be some problem with the include/exclude preference settings. Right now they're
Exclude: {*.{o,pyc},Icon\r,CVS,_darcs,_MTN,\{arch\},blib,*~.nib}
Include: {.html,.tex,.txt,.tm_properties,.htaccess}
Non-text files: {*.{ai,bz2,gif,gz,icns,ico,jpg,jpeg,m4v,nib,o,pdf,png,psd,pyc,rtf,scssc,tar,tbz,tgz,tif,tiff,xib,zip},Icon\r}
Thanks in advance.
The include pattern tells TextMate what you want included.
Set it to * to include everything (except hidden files). The default is: {*,.tm_properties,.htaccess} which includes all non-hidden files and additionally files named .tm_properties and .htaccess (which are normally hidden).
In your pattern, you have set it to only include 5 files.
I assume what you want is something like: *.{html,tex,txt}. Though by explicitly including these file types, you indirectly hide all other file types.
I had a similar problem after messing up the settings.
To fix it, I just deleted:
~/Library/Application Support/TextMate/Global.tmProperties
Related
Recently I scaffolded a project with webapp generator. It created two files .gitignore and .gitattributes. Both show a file extention of type Text Document But when I press F12 to edit any one's name then it has empty name. Here is the snapshot:
My question is why don't window show the name as .gitignore?
There is nothing special with those files. This visual guide may help you.
Also in Windows 10 you may simply try this option in View Tab of Folder Explorer:
After looking and reading closer, it seems that the "problem" is that with the default settings of Explorer "known" file-name extensions (like e.g. .txt) are just not shown.
So if you name a file .txt (full file-name) then it will show up as empty and with no name.
Dot-files are not having any "extension" to their file-name. The full file-name of e.g. the Git ignore file is .gitignore.
It comes from the Unix world where file-names doesn't have to follow the DOS and Windows name.ext scheme, and means that the file is hidden.
Windows since long allows arbitrary file-names as well, but in a name.ext scheme such files doesn't have a "name" only an extension.
Windows interprets .gitignore as an empty file name with the extension "gitignore", and thus shows an empty name be default. To properly see its name, open the folder's properties and check the "Show All File Extensions" option.
I don't have an answer, but I have a preference. I'd prefer not to show all extensions just to be able to see my .gitignore files in Windows10 file explorer.
I'm hoping to extend OP's question by showing I DO SEE .babelrc and .eslintrc, and w/o seeing all file extension setting being set to "on".
It seems, on my own system, that the associations for BABELRC and ESLINT(RC|IGNORE) are, maybe, set automatically by VSCode? In any case, why can I see those "." files, while the in.json is showing with hidden extension, but I can't see .gitignore?
I've read that you can save a ' project ' but apparently I'm doing it wrong.
What I've done is...
Create a js, html and css file and use view/layout with 3 columns so
each file has its own section of the layout.
I then went to Project / save project as / and saved the respective file in
a directory
I assumed that all files should be saved in this directory along with a file that I can click that loads them all up to reflect the workflow.
Apparently sublime has a different idea of how this should work and I do not understand it.
Essentially, there are two parts to a Sublime project - a .sublime-project file, and a .sublime-workspace file. Please see both the "unofficial" docs and the official website for information regarding projects, and the setup of .sublime-project files. These files are JSON-formatted and contain paths to any folders contained in your project, project-specific settings, and project-specific build systems. This file can (and should) be edited to customize the project to your needs. Double-clicking this file (after associating its file type with Sublime, following the procedure of your operating system) will open the project, any open files within it, and any folders you've added to it (by selecting Project -> Add Folder to Project).
The .sublime-workspace file is also JSON-formatted, but is saved automatically by Sublime and shouldn't be edited unless you really know what you're doing, and even then you probably shouldn't edit it. It contains all sorts of meta information about the project's history in Sublime, which files were open and in what order/pane, previous contents of searches, find/replace, etc., your file history, settings for various plugins like SublimeCodeIntel, and lots more. By default it is hidden when viewing the contents of folders in the Side Bar, and when double-clicked it will try to open the project instead of opening for viewing/editing, so there are several measures in place to prevent your playing with it and potentially screwing up Sublime.
.sublime-project files can be saved wherever you want, but the folders and files contained within it are not necessarily saved in the same place - they stay wherever they were saved. It usually makes sense to save them in the project's root directory, so if you have a filesystem like myhomedir/projects/web/SweetWebsite/ containing html/, js/, and css/ subdirectories, you might want to save your project as .../SweetWebsite/SweetWebsite.sublime-project, just so you know at a glance what files/folders are probably in it. However, you could save SweetWebsite.sublime-project in myhomedir/Desktop for all Sublime cares, and it would work exactly the same way. While it is possible to have unsaved files in a project, of course it's always best to save your work early and often, so you don't lose anything.
Hopefully this helps, please let me know if you have further questions.
In an XCode project, all of my source files show up in red in the navigator. Double clicking on them does not open them in the text editor.
The file paths are all correct in the file inspector, though, and the project compiles perfectly well.
It's as if the compiler part of xcode can find the files, but the text editor part can't.
Can anyone suggest how I might fix the project so that I can open the source files in the editor?
Curiously, I've tried deleting and re-adding the them, but this doesn't seem to work. The file names still show up in red.
Any ideas?
Here is something similar that happened to me in git that may help. If you had recently changed the directory path of those files so that one of the folders in that path have a "/" in its name, that could cause your files to turn red and inaccessible.
Hope that is it.
Hm. Originally, all the troublesome files had a variable in their path, e.g. $(MY_LIBRARY_LOCATION)/src/file.cpp.
Originally MY_LIBRARY_LOCATION was an absolute path ( /Users/me/my_libs'). I first tried changing it to a relative path (../../../my_libs`). This didn't help.
Finally, I opened up the XCode project file (myproj.xcodeproj/project.pbxproject) in a text editor and removed all references to the variable. Instead I hard-coded the absolute paths to all the files (e.g. /Users/me/my_libs/src/...). This solved the problem.
It's neither elegant nor portable, but, hey, it works.
I found this too, after moving a project to a new directory.
But I changed the File Path to Absolute in file inspector and it found them all.
Not sure its the best way. BUt it solved my problem quickly
(quick and dirty sorry!)
A
I'm writing an app for the iOS in XCode 4 and stumbled upon an issue with #import statement.
All my source files are organized in folders, every folder is mapped to the group or subgroup in XCode. Consider the following:
ProjectFolder
-SubFolderA
--FileA.h
-SubFolderB
--FileB.m
Usually, if I want to import FileA into FileB, I write #import "FileA.h", and it works perfectly. But sometimes I have to write relative path, like #import "../SubFolderA/FileA.h" . What should I do to be always able to write only name of the file?
This behavior seems undetermined to me.
PS: I don't want to keep all this mess in one root folder.
PS#2: Yes, I know how the 'folder' differs from 'group'. I've created folders on the early stage of the project, dragged them from Finder to XCode and mapped them to groups. And everything worked just fine - I was able to import headers using only filenames.
Search "Scan All Source Files for Includes" in your project's and target's build settings and change the value from "NO" to "Yes". It will solve this issue.
You can always set the "Header Search Paths" under build options to specify which directories to search in. Don't confuse folders and groups though. They are completely independent. In particular groups are simply a convenience that allow you to organize your files within Xcode.
XCode is very much like iTunes in some respects, it wants to manage your files and hide them from you. When you create a group in XCode it's appearance is that of a 'folder' but if you go into the actual project folder you'll still see files everywhere.
Why do my T4 templates sometimes append a number to the output file and sometimes not? For instance, in one case I might have a template file called Foo.tt and I'll get an output file of Foo.cs. In other cases, I'll get an output file of Foo1.cs. In every case, there is no other Foo.cs file that might be causing it to append a number. In other words, it is definitely not the result of any obvious file name conflict.
I'm a deeply anal retentive developer, so I'd sure love to know how to get rid of that useless numeric suffix.
This happens when Visual Studio gets itself confused and briefly decides that it can't use Foo.cs as the output for some reason (usually hallucinatory), so it will use Foo1.cs instead, and then insists on remembering this setting.
The fix is to open the .csproj file in a text editor and locate the Foo.tt entry. This should have a sub-element called LastGenOutput. Change this back to Foo.cs, save the project file, and reopen it in VS.
And then -- sigh -- wait for it to happen again. You can see http://social.msdn.microsoft.com/Forums/en/linqtosql/thread/0c0f77a6-d712-43d2-a990-555df7960123 for more details, though nobody seems to be able to explain what causes VS to get into this state or how to stop it doing so...
#itowlson's answer really helped me out, but I discovered a slightly simpler workaround that I thought I'd share.
If you have:
Filename.tt
└── Filename1.cs
Just rename Filename.tt to Filename2.tt:
Filename2.tt
└── Filename2.cs
And back to Filename.tt again:
Filename.tt
└── Filename.cs
Voilà.
I've discovered something in VS2019 that might explain one potential cause of the issue.
In the CSPROJ file, VS expects a TT file be included using <Content Include="Generator.tt"> tags. When adding a TT file to a project via Cut/Copy/Paste using the contextual menu items in the interface built into VS, VS may sometimes use the wrong XML tag, such as <None Update="Generator.tt">. This will be despite the fact that if you open the Property sheet for the TT file, it will show 'Content' as the build action.
Open the CSPROJ file, and if you change the <None> tag to <Content> and also the Update attribute to Include, then restart VS, the issue appears to go away.