SpaceFM 1.0.0 Released
SpaceFM 1.0.0 has been released. Please see the SpaceFM News page for changes in this version.
Did you know that SpaceFM is a systemd-free file manager which also supports eudev as a replacement for udev? When used with udevil or another mount solution, SpaceFM can be used completely without systemd, consolekit, policykit, dbus, udisks, gvfs and fuse (although it can coexist with and use any of these).
13 Comments
Sorry, the comment form is closed at this time.
Excellent stuff and congratulations :)
Thanks Paul.
Been putting of changing WM
Well, there’s no excuse now
Should try this one
Thanks.
Just to clarify, SpaceFM is a file manager, and it includes a simple and very extensible desktop manager (DM). However, you will still need to choose a window manager (WM). Openbox is a good choice. So Openbox WM with SpaceFM’s DM makes for a lightweight system – no need for a full desktop environment (DE) such as Gnome or KDE. You can just choose your own apps and daemons.
Users and developers are invited to help test the ‘book’ branch of SpaceFM, which includes some changes to bookmarks and will eventually become version 1.0.1. Thanks for testing.
Is it possible that you also upload precompiled binary or something like “PortableLinuxApp”?
No, I don’t get into that anymore. You might ask your distro to package it. See your options here. In general SpaceFM is very easy to build/install, even just from the README.
FWIW, “v1.0.0-1” has already been added to debian’s “sid” repository.
https://packages.debian.org/sid/spacefm
Is/Will be/ it possible to run second instance of spacefm while another one is already running? It could be more useful to test new/next release.
This isn’t officially supported and no plans. You can force two instances by deleting or making inaccessible SpaceFM’s socket in /tmp after the first instance starts. You may want to use a different configuration dir for each instance. For additional info or to add your own comments please see this old issue.
I am a new SpaceFM user. But I can already say: I like it. Thank you for this alternative. But I have a problem or feature request:
I like the output of custom commands in a terminal using this command line:
Menubar/View/Preferences/Advanced:
Terminal: xfce4-terminal –disable-server –hide-menubar –geometry 120×71-0+0 –hold
Maybe you can see my “problem” already. For example, the terminal called with F4 will also show up with –geometry 120×71-0+0 (on the right side of the screen). Or maybe for some custom command I like another –geometry (e.g. 80×71-0+0). Or maybe for some custom command I don’t want –hold. Or maybe for some custom command I prefer xterm over xfce4-terminal for some reason. And so on.
So let us have a command line for the terminal per custom command. But let us also have a default command line in the preferences:
Menubar/View/Preferences/Advanced:
Default Terminal: xfce4-terminal –disable-server
Default Terminal for custom commands (if empty: same as above): xfce4-terminal –disable-server –hide-menubar –geometry 120×71-0+0 –hold
If not overridden in a custom command, this default command line in the preferences will be used.
So I mean: a default command line for the terminals for custom commands in the preferences, but overrideable per custom command.
(Note: it’s “backward compatible”. If someone get a updated SpaceFM with this feature and don’t have a look at the feature set, he will not recognize any change: all his custom commands are working exactly like before. It’s not an “intrusive” change, just an “opportunity giving” change. Also I think it’s a “low hanging fruit”.)
But don’t get me wrong: For now I can live pretty well as it is. I have just migrated all the custom commands from Thunar (except the unzip-stuff) and I am happy. Yes, there are some imperfections or inconveniences because of the lack of said feature, but – for now – I can call these peanuts. I don’t see big dark clouds hanging around here. It’s just a feature request.
A few suggestions on this… For one, you should be able to enter your custom terminal options into the Terminal box in Prefs already.
As for an individual command running in a different terminal, I probably won’t add this as a built-in feature as I don’t see a wide enough call for it, and options are a premium to keep the interface light. Yet there are some things you can do. You can turn off Run In Terminal and Run As Task options, and simply use the command box to run your terminal directly, with the command inline or in a separate script (or even in the same script if you make it conditional). ‘Run In Terminal’ is merely a convenience for running a command in the terminal of choice.
If I wanted to do what you’re saying, I think I would use a script template like this (and you can set it as your default new script in SpaceFM):
$fm_import if [ "$1" == "runme" ]; then shift # put your real commands here else xfce4-terminal --disable-server --hide-menubar \ --geometry 120x71-0+0 --hold \ --command="bash $0 runme" fiThat way you can use the built-in script management and editor, and at the end of your script you can optionally adjust how each command is run. Just disable the Run As Task and Run In Terminal options to run the above script. (Or if you use Run As Task, you should probably use xfce4-terminal option ––disable-server). You could also put some settable options at the top for how you want the script run, to be used in the else block.
Also, in case the above script isn’t clear to anyone, when SpaceFM runs it, it will do so without the “runme” option, so the else block will execute and run the terminal. In the terminal you’re running the command: “$0 runme”. $0 is replaced with this script’s own pathname in bash, so it runs the script again, in the terminal, and this time with the runme option. This will execute the ‘real commands’ section in the terminal. Untested, but that’s one basic idea and should work fine.
Welcome to SpaceFM, hope you enjoy it – you sound like a target user.
I am sure you have users like me in mind when you work on SpaceFM.
Don’t ask me why, but for some obscure reason it was not clear to me that I can just turn of both: “Run As Task” and “Run in Terminal”, and have then the full control what to run. That’s what I am looking for in the very beginning, but overlooked somehow. And by using your script template, we even have something similar to the “overrideable default”. So I don’t need the proposed feature.
Thank you for the input and for SpaceFM.