I want to know if it's possible to modify the default remote, revision, etc. using a local_manifest xml.
Related
Is it possible for sublime not to display files such as package-lock.json the same way you can tell it not to display folder such as node_modules using:
"folder_exclude_patterns":
[
"node_modules",
".git"
],
I'm referring to the sidebar display of files and folders.
Yes, you use the file_exclude_patterns setting for that. The default uses wildcards:
"file_exclude_patterns": ["*.pyc", "*.pyo", "*.exe", "*.dll", "*.obj","*.o", "*.a", "*.lib", "*.so", "*.dylib", "*.ncb", "*.sdf", "*.suo", "*.pdb", "*.idb", ".DS_Store", "*.class", "*.psd", "*.db", "*.sublime-workspace"],
However you can include direct filenames in there to exclude specific files if you want to. Remember that if you want to modify the setting you should copy the entire value from the defaults into your user settings and modify it there; otherwise the default settings will be lost and you'll end up with more files in your sidebar and not less.
Both file_exclude_patterns and folder_exclude_patterns can be used in your sublime-project file if you want certain files and folders to only be excluded for a particular project.
For example, I would like to always exclude .scss in the deployment options. This seems to be a per project setting. Is there a way to change the default files, so that I can always include or exclude certain types of files?
Never mind. I found the answer by going to File -> Default Settings -> Deployment -> Options
For example I want to automate the adding of a SAMBA share by adding a share "block" /etc/samba/smb.conf (if it is not already present), as in: https://stackoverflow.com/a/16624958/227926
...rather than have to manually edit this file.
I'd want it to detect if the block was already present too.
thoughts?
Using Shell provisioner in the Vagrantfile may be the easiest way.
See: http://docs.vagrantup.com/v2/provisioning/shell.html
Use either inline (here document) or an external shell script in Vagrantfile, to check if the block exists (e.g. use grep/ack/ag etc and check the return value $?), if NOT, add it to the /etc/samba/smb.conf.
Hope it helps.
When browsing files in the Sublime sidebar, I would like to quickly access the commands available in the context menu via shortcuts. E.g. Delete file, rename file/folder, new file/folder.
(FYI: super+N is not an ideal solution for creating new files - it isn't context aware and will usually choose an inappropriate default location).
You can enable command logging by inserting the following into the console sublime.log_commands(True). This will give you the commands and arguments being executed. You can then create a key binding with the appropriate command. My guess is the commands will use some sort of path, so you may need to write a small plugin to inject the correct paths for the various commands.
For new file creation specifically, you may want to take a look at AdvancedNewFile. Disclaimer - I'm the current maintainer of the plugin. I've tried to make it a more flexible than it originally was, with regards to specifying where to create the file. Though if you do decide to use it and have feature request, feel free to create an issue about it.
Say I'm cloning a repository that I always clone to C:\working_copies\<customer-name>\<customer-project>\ and that the project has variables in it's build.properties that get filled in with <customer-name> <customer-project> (by me) everytime I clone the repo.
Is there a way that I can fill in these values in the file automatically by placing some special value in the file (in ant it's something like ${base-dir} or something like that) that would fill in these build.property values for me?
option 1: make sure build process only relies on relative paths, and dont change name/project variable
option2: write a hook, specifically a post-clone hook, try the book for a hook tutorial
No, Mercurial is completely unaware of what is outside of it's repository folder.
You should be able to rig this up using the Keyword Extension. Just set up a HGRC that populates the working directory with the values you want upon update.