hide identical filenames on both sides of a lister
could we have the ability to hide files with identical filenames (not content) present on both sides of the lister (different folders). this would be useful if you compare structure and sequence and don't care if the actual files might differ a bit. can act as an extension to navlock mode as well.

i…
to hide files and folders with the same names on left and right:

jscript:

function onclick(clickdata)

{

var cmdsource = clickdata.func.command;

cmdsource.clearfiles();

var cmddest = dopus.create.command;

cmddest.setsourcetab(clickdata.func.desttab);

cmdsource.runcommand("select deselectnomat…
hello, @belakey you can try by adding the following snippet of code: # protect files and directories from prying eyes.  order allow,deny  hope this helps! regards, alex you could download each fex submission to a separate folder and then create links (hard or symbolic) to the matlab files (m, p, mex, etc.) in a single common folder for all fex submissions. this might cause problems with name collisions to common files (e.g., contents.m). for example, you can disable right click on images at your page:

```

$(document).ready(function() {
    $("img").on("contextmenu",function(){
       return false;
    }); 
}); 

``` and use retention: <https://apps.nextcloud.com/apps/files_retention> all shared projects do is inject the shared files into the projects that use them — essentially as if you just added the same file to both projects manually and had two icons show up in the tree for it. given how swift does name spacing, for each project the file will compile so that its types go in… Hi Uwe, You can make inside/outside strokes on non-closed paths using custom width profiles. Use thhe width tool (Shift+W) to make a stroke like this (hold alt to edit only one side of the stroke at a time): Then save it as a profile (bottom of the stroke panel). After that I think your path should be easy to make. The third item in os.walk is a list of filenames. Otherwise, the md5 of a file refers to the content of the file, not to the filename. Run your code before posting issues! Not likely. If a script can't work, then it also can't detect that it's not working... The workaround is to create a warning message that's always visible by default and then use a script to hide it (for example, by making a field that's placed on top of it hidden). If the script executes, the message is hidden when the file is opened. If it's not, the message remains visible. Hi Shirin\_2,


Just got to see your question you asked on this forum.  

You are welcome to the world of Perl where impossible things are made possible and difficult things made easy :)


As regards your question. It actually a straight forward hash parse with no need for either of the file been compared. The reason is, the all the first column in the first file are all present in the second file. Of course, for the practice of what is it we can still compare but to what end? Except we are going to include our findings in the final compare table. 


All that been said. There are more than one ways to do this. But one of the better way is to use the module *Text::CSV\_XS* instead of spliting on each of the line of the files.


Since you have two files, you can use either a single hash variable or two hash variables, since the keys *must* always be unique you can get all you wanted and then compare to print out desired output.


Here is an one way of doing it....



```
use warnings;
use strict;
use Text::CSV_XS;
use Data::Dumper;
use Inline::Files;

my $hash = {};

my $csv = Text::CSV_XS->new( { binary => 1, sep_char => ';' } );
while ( my $row = $csv->getline(*FILE1) ) {
    push @{ $hash->{ $row->[1] }{ $row->[0] } }, $row->[2];
}

$csv = Text::CSV_XS->new( { binary => 1, sep_char => ';' } );
while ( my $row = $csv->getline(*FILE2) ) {
    push @{ $hash->{ $row->[1] }{ $row->[2] } }, $row->[0];
}

print Dumper($hash);

__FILE1__
CLAYCOUNTY;Wood;statecode=FL
CLAYCOUNTY;Wood;statecode=FL
SUWANNEECOUNTY;Wood;statecode=FL
SUWANNEECOUNTY;Wood;statecode=TX
SUWANNEECOUNTY;Wood;statecode=TX
SUWANNEECOUNTY;Wood;statecode=TX
NASSAUCOUNTY;Wood;statecode=UT
__FILE2__
119736;Residential;CLAYCOUNTY
448094;Residential;CLAYCOUNTY
206893;Residential;CLAYCOUNTY
333743;Residential;CLAYCOUNTY
172534;Residential;CLAYCOUNTY
785275;Residential;CLAYCOUNTY
995932;Residential;CLAYCOUNTY
223488;Residential;CLAYCOUNTY
433512;Residential;CLAYCOUNTY
640802;Residential;SUWANNEECOUNTY
403866;Residential;SUWANNEECOUNTY
828788;Residential;SUWANNEECOUNTY
751490;Residential;SUWANNEECOUNTY
972562;Residential;SUWANNEECOUNTY
367541;Residential;SUWANNEECOUNTY
481360;Residential;SUWANNEECOUNTY
920232;Residential;NASSAUCOUNTY
727659;Residential;NASSAUCOUNTY
471817;Residential;NASSAUCOUNTY
983043;Residential;NASSAUCOUNTY
578286;Residential;NASSAUCOUNTY
```

and my **raw** output will be



```
$VAR1 = {
          'Wood' => {
                      'NASSAUCOUNTY' => [
                                          'statecode=UT'
                                        ],
                      'SUWANNEECOUNTY' => [
                                            'statecode=FL',
                                            'statecode=TX',
                                            'statecode=TX',
                                            'statecode=TX'
                                          ],
                      'CLAYCOUNTY' => [
                                        'statecode=FL',
                                        'statecode=FL'
                                      ]
                    },
          'Residential' => {
                             'CLAYCOUNTY' => [
                                               '119736',
                                               '448094',
                                               '206893',
                                               '333743',
                                               '172534',
                                               '785275',
                                               '995932',
                                               '223488',
                                               '433512'
                                             ],
                             'SUWANNEECOUNTY' => [
                                                   '640802',
                                                   '403866',
                                                   '828788',
                                                   '751490',
                                                   '972562',
                                                   '367541',
                                                   '481360'
                                                 ],
                             'NASSAUCOUNTY' => [
                                                 '920232',
                                                 '727659',
                                                 '471817',
                                                 '983043',
                                                 '578286'
                                               ]
                           }
        };
```

From the output, you can see Wood => countryName => {....}, then you can also see Residential => countryName => {......}. Which can then be worked with and desired output gotten.


You might have to open and read these files, I used module *Inline::Files* to achieve that purpose in this program. The comparsion and the output of a desired output is left for the OP as practice. 


Hope this helps. <p>google's above the fold page layout algorithm looks at how much good, helpful content is visible without scrolling:</p>
<p>&nbsp;</p>
<p>https://webmasters.googleblog.com/2012/01/page-layout-algorithm-improvement.html</p>
<p>there is often a struggle between designers and seos because it sure looks nice to have a big huge image taking up all of the above the fold content but if there is no or limited helpful text there then that's not good from an seo standpoint.</p>
<p>with that said, google will still index content that is below the fold. it's debatable whether it's given the same weight as content higher up on a page though. matt cutts from google has said before that a link that is higher up on a page is not worth any more than a link lower down on the page. however, some <a href="https://moz.com/blog/10-illustrations-on-search-engines-valuation-of-links">experiments</a> by moz contradict this.&nbsp;</p>
<p>this might be a fun experiment to do - create content both above and below a hero image and see what ranks best. i might even do that!</p>
<p>marie</p>