I'm trying to exclude all subfolders except for one. I've seen wild cards to include and exclude, is there a way to "exclude all except" ?
An example might make it easier to see what I'm trying to do.
Let's say I have a workspec like so:
//depot/Root/... //PC/Root/...
Under root there are some platform specific files. If I am working on platform D I don't care about platforms A,B,C. Currently I have to do something like this:
-//depot/Root/Binaries/A/... //PC/Root/Binaries/A/...
-//depot/Root/Binaries/B/... //PC/Root/Binaries/B/...
-//depot/Root/Binaries/C/... //PC/Root/Binaries/C/...
Imagine that there are a few subfolders I care about, and many that I don't want. Is there a way to specify something like, exclude this entire folder except for these subfolders?
I tried playing with the order of the workspace mapping but that didn't seem to make any difference.
I guess you want to exclude all the direct subdirectories of Binaries other than D, but keep everything else under Root. How about something like this?
//depot/Root/... //PC/Root/...
-//depot/Root/Binaries/... //PC/Root/Binaries/...
//depot/Root/Binaries/D/... //PC/Root/Binaries/D/...
Related
Is there any way to exclude certain directories when searching a particular github project?
In a large project on Github like nodejs, I often want to search the source code to find where in the project something is defined. A challenge I regularly run into is that the project itself contains hundreds of files related to module tests and these test directories clog up the search results when I'm trying to find something in the actual source, not in the testing code. So, instead of getting 5 pages of results to look through, I might get 50 pages of results, rendering the search somewhat useless.
In the nodejs project, I'd like to search without including the top level "test" directory.
To search in one particular directory you can use:
searchterm path:/lib
And to ignore a directory you can use:
searchterm -path:/test
As mentioned in your comment, the official documentation is here. An answer on how to ignore stuff can be found here.
I'd like to get a few things cleared up about playlist folder handling in Libspotify. A few things seem a bit inconsistent about it (I get the impression folder handling has been hacked in as a bit of an afterthought?)
When I cycle through all the playlists in a container, I notice I get the same sp_playlist handle value for all the folders. This means I can't use any of sp_playlist_xxx functions on folders, right? So I can't register callbacks on them, cannot find out their name, etc?
Instead, I have to use special functions on the PlaylistContainer to get folder names?
Is it dangerous to use sp_playlist_add_ref and sp_playlist_release on handles pointing to folders?
Also, what is the sp_playlistcontainer_playlist_folder_id function intended for?
Your assumptions are mostly correct. Folder placeholders in the playlist container list are just that - placeholders.
Instead, I have to use special functions on the PlaylistContainer to get folder names?
Yes, sp_playlistcontainer_playlist_folder_name().
Is it dangerous to use sp_playlist_add_ref and sp_playlist_release on handles pointing to folders?
Not especially, as long as you don't over-release somewhere, but that's true of everything. You'll just have multiple owning references to the placeholder, which is fine.
Also, what is the sp_playlistcontainer_playlist_folder_id function intended for?
It's a unique ID for the folder, mainly there since you can't use the pointer as a unique identifier since all folders use the same placeholder object. It allows you to compare folders to one another without doing string comparison on the name (which, since multiple folders can have the same name, isn't actually a good idea).
At the moment when you go to select an image inside an entry using the EE default file manager, the default view is 'show files as a list'.
Is there a way to show the thumbnail view as the default?
At this point I would be happy with a core hack.
I don't usually use the file manager for sites (much prefer Assets) but this client had a tight budget
I've wondered about doing this in the past as well - turns out it's pretty simple. Open up ee_filebrowser.js and search for the first instance of a("#dir_choice").val(). Immediately after that add this:
; a("#view_type").val('thumb').change();
Make sure you include the leading ;.
I've only tested this in Safari but I can't see why it wouldn't work everywhere. Incidentally, JS beautifier makes this sort of thing infinitely easier.
I don't recommend hacking core for any reason and I suggest it should be avoided at all cost.
With that said, I will provide what I've found out just the same.
Looks like the following files, in EE 2.5.3, are what you'd want to edit:
/themes/javascript/compressed/jquery/plugins/ee_filebrowser.js
/system/expressionengine/libraries/File_field.php
I found these doing a file search in my text editor for view_type which was from the id of that dropdown. The javascript is minified so you'd probably want to un-minify it and then rewrite the part which handles the switch. I'm not the best JS/jQuery person out there, and un-minified js makes it a bit harder too so, I won't offer any more than what I've found so far.
Consider pulling out the parts parts from the two files if you aren't great with js and maybe start a new post tagged accordingly.
Also note: there might be more to this than just those two files so consider this answer a start and nothing more.
Is there a way to check what is the target of a link, using NSIS ?
[ I want to check and update links on desktop, but I have a hard time checking if they belong to my application, because the name may contain a space or something, so it may not be identical...
I also want to delete links that are no longer used, that point to my folder.
So... I would like to look at the target, but can't fins anything that gives it to me. ]
You could try the ShellLink plugin or call the IShellLink+IPersistFile COM interfaces directly with the system plugin but normally a uninstaller/updater will only deal with shortcuts it created and not things the user might have created/renamed...
I work on a number of sites that compartmentalise controllers into folders -
e.g.: news/index.php, news/view.php, pages/index.php, pages/view.php, etc.
I'm finding it very difficult to use Dreamweaver to edit these sites as the tabs and title bar only shows the name of the document and I get lots of "index.php", "index.php", "index.php" documents that are impossible to differential from one another unless I actually load them and look at them.
Is there a solution to display the parent folder somewhere, e.g.: "pages/index.php" instead of just "index.php"?
Thanks.
I do not think so. you better name your files with different names. than with a different directory. it's just my advice. good luck!