Arch Linux User Repository

@rien333 I cannot reproduce that in a clean chroot build environment. I believe it to be completely unrelated to the author's GCC 10+ fix. There is no pkgver update because the upstream project's version has not changed (though it is arguable that it should have been). What version of gcc are you using? Are you using an AUR helper?

I can't get 0.6-4 to build. I get:

Browser.cpp: In member function ‘void fim::Browser::push_shadow_dir(std::string)’:
Browser.cpp:1113:17: error: ‘push_dir’ was not declared in this scope; did you mean ‘is_dir’?
 1113 |                 push_dir(fn,FIM_FLAG_PUSH_REC,NULL);
      |                 ^~~~~~~~
      |                 is_dir
make[4]: *** [Makefile:878: Browser.o] Error 1
make[4]: *** Waiting for unfinished jobs....

Maybe the 'gcc 10' patch shouldn't be reverted after all? Or is this an unrelated error, caused by the developer trying to fix compilation support for GCC > 9? I see the shasum changed, but no corresponding pkgver update?

@m040601 I'm happy to be able to contribute, and glad to hear you're using fim as well. I still use it every once in a while to help with generating art. Well over two years later, the upstream author graciously decided to fix compilation support for GCC > 9, hence the update.

Setting FBFONT isn't really required. This message is a carry over from a previous maintainer. I'll likely remove it in the future, unless someone can offer an argument to keep it. More information about its usage can be found here.

There is this "fim.install" source appended to this PKGBUILD that produces this output during installation,

:: Processing package changes...
(1/1) upgrading fim                                     [##############################] 100%
==> NOTE: If you already have FBFONT exported correctly, you can disregard this
==> message.
==>
==> To get fim to work after you've installed it, place the following export in
==> your ~/.profile file:
==>
==>   export FBFONT=/usr/share/kbd/consolefonts/ter-216n.psf.gz
==>
==> Once this is done, log out and log back in to get your ~/.profile file
==> read and the FBFONT variable exported.
==>
==> NOTE: If you place this export in your ~/.zshrc or your ~/.bashrc file, you
==> don't need to logout. Simply starting a new session of your shell-of-choice
==> will do the trick.
:: Running post-transaction hooks...

Not sure if the above information/warning is still valid ???

I'm not sure if it is only me. I dont use a desktop. I dont start X. I work in the Linux Console.

I dont do this "export FBFONT". I dont have any environmental variable "FBFONT". And I never had any problem with fim.

@andrew

Thanks for your work maintaining this PKGBUILD. Much appreciated.

I got a surprise, today when it got updated. I thought I was the only one using this tool. And that nobody else cared. Last update was 2020.

Decided to check out how thing are upstream.

The mailing list hasnt seen any activity since 2019, http://lists.nongnu.org/archive/html/fbi-improved-devel/

But the git repo still seems active, http://svn.savannah.gnu.org/viewvc/fbi-improved/trunk/?sortby=rev. Uses subversion ? not git ?

Anyway.

This is a very usefull and underrated tool, that works perfectly in the Linux console. No need to start a desktop. No need to start X.

A very powerfull alternative to "sxiv" like image viewers for the desktop.

I use it to preview and/or open images in the text browser w3m, with mutt, rss client etc.

It also has very powerful scripting capabilites to do lotz of interesting things. Havent tried all of that yet.

Although I find it's extensive documentation and tutorial a bit overwhelming, convuluted and disorganized. Pity I can't find more Archlinux wiki pages, forum topics and users interested in these framebuffer tools.

Thanks. (It is/was just my local setup that is/was messy.)

bison and flex are pulled in by base-devel. Per PKGBUILD guidelines, these should not be a part of makedepends.

May it be that bison and flex should be in the makedepends?

Thank you, @garron.

I added this to the PKGBUILD after configure to get it to build in GCC 10. Note that this disables multithreading, and so should not be considered a proper fix.

  sed -i -e 's/#define FIM_WANT_BACKGROUND_LOAD.*//' src/fim.h
  sed -i -e 's/void exit/FIM_NORETURN void exit/' src/CommandConsole.h
  sed -i -e 's/°//g' src/fim.cpp