Skip to content
Snippets Groups Projects
  1. Aug 31, 2016
    • Niclas Zeising's avatar
      Only use sysconf() if HOST_NAME_MAX is undefined · 5ab630b5
      Niclas Zeising authored
      On some systsems sysconf() can return a very large value, unsuitable for
      use with malloc().  Only use sysconf() if HOST_NAME_MAX isn't avalable.
      5ab630b5
    • Niclas Zeising's avatar
      Fix build on FreeBSD. · 873c84f0
      Niclas Zeising authored
      FreeBSD lacks the constant HOST_NAME_MAX, instead using sysconf(3) to
      find out the value of the maximum host name length at run time.  Patch
      to use this instead of HOST_NAME_MAX.
      This brings with it the need to use malloc instead of using a statically
      sized buffer for the host name, since the size of the buffer cannot be
      known at run time.  Errors from sysconf or malloc just means that the
      entire block of code is skipped over (the same way it's skipped if the
      call to gethostname() fails), rather than returning any kind of error to
      the caller or logging an error message somewhere.
      873c84f0
  2. Aug 28, 2016
  3. Aug 27, 2016
  4. Aug 23, 2016
  5. Aug 22, 2016
  6. Aug 21, 2016
  7. Aug 20, 2016
  8. Jul 31, 2016
  9. Jul 25, 2016
  10. Jul 24, 2016
  11. Jul 22, 2016
  12. Jun 23, 2016
  13. Jun 22, 2016
  14. Jun 19, 2016
  15. Jun 09, 2016
  16. Jun 07, 2016
  17. Jun 06, 2016
  18. Jun 02, 2016
  19. May 28, 2016
    • guns's avatar
      Add prev_dir and next_dir navigation actions · 36b09fa0
      guns authored
      Many image collections are organized by directory, so it is nice to have
      jump-to-adjacent-directory navigation.
      
      e.g. Given the following file hierarchy:
      
          .
          ├── A
          │   ├── 1.jpg
          │   ├── 2.jpg
          │   └── C
          │       ├── 1.jpg
          │       ├── 2.jpg
          │       └── 3.jpg
          └── B
              ├── 1.jpg
              ├── 2.jpg
              └── 3.jpg
      
      `feh --recursive` creates the following filelist:
      
          A/1.jpg <---- current_file
          A/2.jpg
          A/C/1.jpg
          A/C/2.jpg
          A/C/3.jpg
          B/1.jpg
          B/2.jpg
          B/3.jpg
      
      If we press [next_dir], we move the current_file pointer to:
      
          A/1.jpg
          A/2.jpg
          A/C/1.jpg <-- current_file
          A/C/2.jpg
          A/C/3.jpg
          B/1.jpg
          B/2.jpg
          B/3.jpg
      
      Pressing [next_dir] again moves the pointer to:
      
          A/1.jpg
          A/2.jpg
          A/C/1.jpg
          A/C/2.jpg
          A/C/3.jpg
          B/1.jpg <---- current_file
          B/2.jpg
          B/3.jpg
      
      [next_dir] now moves the pointer back to the top of the list:
      
          A/1.jpg <---- current_file
          A/2.jpg
          A/C/1.jpg
          A/C/2.jpg
          A/C/3.jpg
          B/1.jpg
          B/2.jpg
          B/3.jpg
      
      Pressing [prev_dir] from here moves backwards to the first image of the
      previous directory:
      
          A/1.jpg
          A/2.jpg
          A/C/1.jpg
          A/C/2.jpg
          A/C/3.jpg
          B/1.jpg <---- current_file
          B/2.jpg
          B/3.jpg
      
      When starting from an position that is not the first image of a
      directory, [prev_dir] moves the pointer to the first image of the
      current directory.
      
      These actions combine well with `--sort dirname` since all regular files
      in a directory will be sorted before any subdirectories, avoiding a
      filelist like the following:
      
          A/1.jpg
          A/SUBDIR/2.jpg
          A/SUBDIR/3.jpg
          A/4.jpg
      
      With `--sort dirname` that filelist becomes:
      
          A/1.jpg
          A/4.jpg
          A/SUBDIR/2.jpg
          A/SUBDIR/3.jpg
      36b09fa0
Loading