I have to recoll indexing more than 10000 directories and huge number of files.
My directory structure looks like:
Class1
Class1\Users
Class1\Users\Teachers
Class1\Users\Students
Class2\Users\Teachers
Class2\Users\Students
XXXX\YYYY\Teachers
XXXX\YYYY\Students
...
It is important to don't indexing Students directories.
Where can I set to skip the Students directories on recoll-gui?
I found recoll manual: http://www.lesbonscomptes.com/recoll/usermanual/usermanual.html
and I also found the "skippedPaths" variable, but I don't know the exact format, how can I skipping "Students" directories on the indexing (on recoll-gui).
recoll-gui settings Screenshot
Mod:
Unfortunately, there are "Students" directory everywhere, not only under Users directory. For example there is Student directory under Teacher directory.
Skipped Names is not good, because in the Teacher directory there are documents which called "student-names.xls" and indexing may skipped that document also...
In the GUI, go to the indexing configuration section, and click on the + sign for the Skipped Paths section.
This does not open a file selector because you could conceivably have wildcards in there.
Just copy the path for the Students folder as seen on the Linux machine. You can probably see an example path in the "Top directories" section as you must have added something in there.
There will be no backslashes in the path, of course.
Ok, second try: I now understand that you have many "Students" directories, maybe a huge number. If this is the case, you should probably use the "Skipped Names" parameter instead. Go to "Indexing parameters" - "Local parameters" and just add "Students" to the "Skipped names" list (globally: no need for anything in the "Customised subtrees" section)
Related
I have a simple issue with zsh. Sometimes, I am in a directory with multiples sub-directories.
So, when I do a $ ls[TAB] or $cd[TAB], I list all these sub-directories.
But how to accept one of the suggestions for sub-directories? Is there a short cut or a key to choose a directory to go deeper in this directory.
I must precise that I don't know systematically the content of these subdirectories, so I can't often choose a subdirectory in which the first letter of filename could allow me to choose automatically the sub-directory to explore.
I was looking for a solution on the web but documentation about zsh completion is pretty big.
Edit: simplest solution to accomplish the desired effect:
press [/] key to 'accept' the current suggested directory ; then press again [tab] key to show suggestions of its subdirectories
Old suggested solution:
Install https://ohmyz.sh/
Then pressing the [tab] key displays a list and the first item is highlighted.
Hit the [tab] key again to choose the desired item and hit the [enter] key to write it in the command line interface, without actually executing the command, only as if you have just typed it in.
Then you can continue hitting the [tab] key to select another subdirectory, and so on.
It also works on any autocompletable, not only dirs.
The only way I know is: double click your target + cmd c + cmd v and then press Enter.
I'm attempting to incorporate a WordPress website into Git.
I've created a local repository through GitHub for Mac, and I've edited the "Primary remote repository" to the HTTPS URL under the Settings tab, after which I've then applied some ignore patterns.
So far this has worked.
However, when I look at the items under the Changes tab, I'm seeing entries for the ".gitignore" file and everything in the "wp-content" folder but nothing above it.
I don't think it's the ignore patterns because some of the default WordPress templates are in there, and a load of OS items, each of which have been ignored, but I understand the ignore patterns won't be applied until after a commit.
At the bottom of the list of entries to commit, the path is correct and not within the "wp-content" folder.
So why are things like "wp-admin" and "wp-config.php" — or any other root item — missing?
Is there a maximum length to the number of items GitHub for Mac can show, but if so, why show "wp-content" when other items precede it in alphabetical order?
I'm a bit confused as to what's happening. At this point, nothing has been committed, and I'm hesitant to do so if part of the website is missing.
This is the section that's causing it:
#===================================#
# WP Core, except content #
#===================================#
/*
!.gitignore
!wp-content/
# !media/
!favicon.ico
!favicon.png
!robots.txt
!humans.txt
Notice the leading /*. This means that it's ignoring EVERYTHING by default. From the documentation:
A leading slash matches the beginning of the pathname.
The wildcard * then tells it to match everything in that path.
The exclamation point ! then refers to items which explicitly should NOT be ignored.
I see that the ability to specify JSHint options on a per directory basis was added here.
However it is not clear to me how you actually take advantage of this. What do I do to set JSH options in a single directory, so that the options differ from other directories?
It appears that the change in question actually allows you to specify overriding options on a per-file basis. You can add an overrides property to your config, the value of which should be an object. The keys of this object are treated as regular expressions against which file names are tested. If the name of the file being analysed matches an overrides regex then the options specified for that override will apply to that file:
There's an example of this in the cli.js test file diff in the commit you linked to:
{
"asi": true,
"overrides": {
"bar.js$": {
"asi": false
}
}
}
In that example there is a single override which will apply to any files that match the bar.js$ regular expression (which looks like a bit of an oversight, since the . will match any character and presumably was intended to only match a literal . character).
Having said all that, it doesn't look like the overrides property is going to help you. I think what you actually want is a new .jshintrc file in the directory in question. JSHint looks for that file starting in the directory of the file being analysed and moves up the directory tree until it finds one. Whichever it finds first is the one that gets used. From the docs:
In case of .jshintrc, JSHint will start looking for this file in the same directory as the file that's being linted. If not found, it will move one level up the directory tree all the way up to the filesystem root.
A common use case for this is to have separate JSHint configurations for your application code and your test code. This allows you to define the different environments and globals separately.
I have a wxFilenName mydir that should point to a writeable directory. Ultimately, mydir has been obtained via mydir=otherfilename.GetPath() (though via some disgressions maybe). Assuming that mydirrefers to (on a Windows box) C:\foo\bar, I need to ensure that C:\foo\barexists and is a directory (not a file) and I have write permissions (so I might create C:\foo\bar\baz).
What I do is to check mydir.IsOk() && mydir.DirExists() && mydir.IsDirWriteable(), but I suspect this does not do what I want. From reading the wxwidgets docs, I gather that it does distinguish between a wxFileName referencing C:\foo\barin the sense of "the file/dir bar in the directory C:\foo" versus C:\foo\bar in the sense of "the directoy C:\foo\bar and no particular file in it") so that I'd expect my method to work as GetPath()should return such a "pure" directory. However, I suspect (and testing indicates) that my checks really check if C:\foo is a writeable directory ...
What would be a better method (within the wxWidgets framework)? Do I really need to append some dummy filename before performing my checks?
Use wxFileName::DirName() to create an object representing a directory.
We have many old snapshot views lying around and I need to find out when these snapshot views were created.
There is a twist - we are no longer running ClearCase and the hardware we used to run it is no longer around. However, we still have all the files used internally by ClearCase still lying around, so I can go to a directory /usr7/viewstore/some_snapshot_sv and poke around.
I've got a timestamp on these directories, but this is not necessarily when the view was created.
I was wondering if somewhere in this directory structure there was a certain file in which I can search for a creation date.
I'm in a Unix/Linux environment. ClearCase did run on IRIX.
Thanks.
Any metadata associated with the view is on the view server side, where the view storage are kept.
The one file which could be the closest from the creation date would be the .hostname file within a view storage.
It is only created and updated on the view creation, and never change unless the view is unregistered, and then re-registered (very rare).
view.dat is also a good candidate (but can also be regenerated, and is for snapshot view only)
This IBM article lists all relevant files:
Files that are regenerated automatically when the view is restarted:
# .access_info
# .pid
Files that can be regenerated with ClearCase commands:
# .compiled_spec -- regenerate by running cleartool setcs -current
# .hostname -- regenerate by unregistering and re-registering the view
# view.dat -- Snapshot views only:
can be regenerated by running the "regen_view_dot_dat.pl" script
found in <cc-home-dir>\etc\utils
See technote1204161 for more details on the regenerating the view.dat file.
Files that can be manually replaced by making a new view on the same machine as the same user, and copying the affected file(s) to the view storage:
# config_spec
# groups.sd
# identity.sd
# view_db.state (as long as the view is not in the process
of being reformatted); see technote 1134858 for more information
# db/view_db.dbd (for schema 9 views only; 2002.05.00 and earlier)
# db/view_db_schema_version
# .view - The copy obtained from the new view must be edited to contain the correct information for the old view as described below. The correct information can be obtained from the output of "cleartool lsview -long <old_viewtag>".
Line 1: the location of the view storage directory, in hostname:pathname format
Line 2: the view's UUID (unique identifier), which must not be changed
Line 3: the hostname specified in line 1
Files that cannot be replaced:
# All other files in the db directory except the ones mentioned above
( view_db_schema_version and view_db.dbd)
If you use cleartool, I think you may try it this way:
cleartool lsview -properties [view-name]
* [view-name] /net/...[path]
Created 2014-01-07T18:05:15+02:00 by ...
Last modified 2014-01-07T21:13:07+02:00 by .....
Last accessed 2014-01-07T21:13:07+02:00 by .....
Owner: [owner-name] : rwx (all)
Group: [group-name] : r-x (read)
Other: : r-x (read)