All Projects

Safe length measuring creates extra temporary directories that aren’t removed properly

With the introduction of ~/.vcs/ (or ~/.vcs-nix/) it makes sense moving local configurations there. The older ~/.vcs.conf will still be accepted.

Load order:

1. /etc/vcs.conf
2. ~/.vcs.conf
3. ~/.vcs/vcs.conf
4. ./vcs.conf

-I does use it

No need for description

Sometimes a negated type will be ignored.

e.g.:

Fine:

$ relevation -t website java.net

-> Search "java.net" ('website' entries):  1 matches

$ relevation -t -website java.net

-> Search "java.net" ('not website' entries):  No results

Not fine:

$ relevation google.com

-> Search "google.com" ('not folder' entries):  6 matches

$ relevation google.com | grep -c ^Type:\ website
5

$ relevation -t -website google.com

-> Search "google.com" ('not website' entries):  6 matches
$ relevation  -t -website google.com | grep -c ^Type:\ website
5

$ relevation -t website google.com

-> Search "google.com" ('website' entries):  5 matches

Might be due to entries inside folders being repeated?

Parsing of the “-U” option (optional argument) is incorrect, it always receives an argument (empty if none provided) which must be shifted manually. Currently it’s only shifted if provided explicitly.

“–fullname” is not affected since it doesn’t take any arguments.

At least on some systems, the console/terminal needs a manual reset (or tset) to be usable after running vcs.

When repeated captures are avoided, captures end up being filtered more than once

Files should be checked for the appropriate format instead of blindly opening them

Reported by David

The icon and main app can get out of sync on version 1.4

Probably related to FS#255.
1.4 used separate network listeners for notification and main app, with the main app always listening for signal strength changes (and notification doing so optionally).

Sharing from some apps leads to an error and the impossibility to share the file

Reported by Marcel Bokhorst

Starting with Lollipop notifications are shown in the lock screen expanded, and their
contents will be hidden if public visibility isn’t set explicitly.

Android Studio / Gradle support the use of build “flavors” with different code, plus Android apps support versioned resources, so the two branches can be merged into a single one taking advantage of that.

It doesn’t make sense to load on boot if we won’t be displaying the notification.

Reported by Red Rospo 04/08/2016 on Google Play

Da migliorare Non parte al boot

LG G5 (h1) / Marshmallow / r14034

Reported by Simon Howard 18/12/2016 on Google Play

Issue with auto start on boot I’ve had this app for some time now, but it will not auto start on boot on my current phone (Galaxy S5, Marshmallow 6.01)

Galaxy S5 (klte) / Marshmallow / r14034

This setting is shown regardless of version but it has no effect on older Androids since they don’t support notification actions.

See FS#356

Submitted by Davide Cavestro

The array EVASION_ALTERNATIVES isn’t looped over correctly. Correction:

-		for delta in $EVASION_ALTERNATIVES ; do
+		for delta in ${EVASION_ALTERNATIVES[*]} ; do

Reported by remlap

File sizes are displayed as 3.00GiB instead of 3.54GiB

E.g. 4m30s

See http://p.outlyer.net/dox/vcs:time_syntax