Prompt Command File Manager: tiny bash FM

Last year pyfmii, now this. What's with these crazy file managers.
http://paste.pocoo.org/show/175499/
wget http://paste.pocoo.org/raw/175499/ -O ~/bin/pcfm; chmod +x ~/bin/pcfm
PROMPT_COMMAND=pcfm
By avoiding ncurses the program only takes up a few lines and doesn't clear the screen (and speed is still OK). It can paste right into the bash prompt using xdotool and xsel for a very transparent approach to the "subshell" in some file managers (like mc).
Features include bookmarks (you can actually call the program as a general selector for a list (try pcfm ls /)), sessions to keep track of last selected/marked files in a dir, searching in the list, some navigation things like trying to find the closest match when the previously selected item was deleted and auto-selecting the parent directory on `cd ..`, and a launcher for filenames.
It can generate the file list with any command you want, but will need a few functions to get the filename, and tell whether it's a directory and such. I have added a few of these "profiles".
The bad thing is that it needs xdotool and xsel, which I mentioned in this thread. xdotool can give bugs (I ran into shift lock a lot, which can be avoided by using an emulated click instead of Shift+Insert), will be a bit slow, and when you use it to paste, the mouse needs to be on the window. I actually wrote a function that moves the mouse on the window! So that is quite bad.
On the other hand, if a string only has ascii ([[:print:]] in C locale), it can be typed by `xdotool type --window xxx ...`, and xsel and pasting won't be needed. This speeds things up and makes it a little more stable (mouse doesn't have to be on the window, etc).
Anyway, if you use screen and like this file manager, be sure to try the different approach in the linked thread.
Screenshot:
Screenshot? Try your ls alias. On a related note, make sure you have a good LS_COLORS variable.

EDIT: wget 'http://echtor2oo3.de/paste/9769876.txt' -O - | tr -d '\r' > ~/bin/pcfm; chmod +x ~/bin/pcfm
(before edit version: 'http://echtor2oo3.de/paste/7936610.txt', it didn't restore selected files if you didn't have a dir-specific profile)
github and an rc file is a bit too much for a tiny program. In a case like this, an rc file is good if you have frequent updates, but unless someone has more good feature requests, there won't be anything to update. (new profiles, keybindings, file associations, it's all up to the user)
I made the start of the file look more organized so it's easier to change. Note that F9 takes you immediately to edit the script.
find-as-you-type searches the entire line: directory entries start with d.
alias is a good idea (up to the user), auto-setting the prompt requires sending a command, so that's too tricky.
I added a command line switch -t, to set the default profile.
The profile keys are now:
^H: toggle iso / iso-no-hidden
(commented) ^H: iso-no-hidden
^S: time sorted (based on iso)
^E: extension sort (based on iso)
^T: traditional (full ls -l)
^I: iso (-g -G and long-iso time) (^I is also TAB)
^N: minimal (size, filename, ID character)
^U: custom (e.g. `find -maxdepth 1`, it brings up a prompt), since directory status can't be checked (actually you can, with `file`, I will look into it later), you have to type F2 and cd
^P: show the profile list and choose one (like bookmarks)
Last edited by Procyon (2010-02-13 13:28:46)

Similar Messages

Using bash as your file manager?

Hello,
My belief is that all file managers suck. There are no exceptions to this. So, for the past few months, I've been sourcing a file with a bunch of tricks I've invented / found through browsing the web to make using just bash as a file manager much more convenient.
Here's what I currently use:
# fm v1.9.1 by Kiah Morante
# A very simple file manager.
# Depends on pycp/pymv, http://github.com/yannicklm/pycp and feh
# 'source' this file in a BASH shell
showHidden=0 # Hidden files not shown
showDetails=0 # ls is replaced with ls -lh if showDetails is 1
shopt -s autocd # cd to a dir just by typing its name
PROMPT_COMMAND='[[ ${__new_wd:=$PWD} != $PWD ]] && list; __new_wd=$PWD' # ls after cding
# Shortcuts
source ~/.config/fm/shortcuts # Call all custom shortcuts
alias ..='cd ..'
alias ...='cd ../..'
alias ....='cd ../../..'
alias h='cd ~'
alias n='cd "$n"'
# Keybindings
bind '"\C-l":"list\C-m"'
bind '"\C-h":"hide\C-m"'
bind '"\C-o":"details\C-m"'
bind '"\C-f":"makedir\C-m"'
bind '"\C-n":"n\C-m"'
bind '"\C-y":"cpwd\C-m"'
bind '"\C-p":"cd "$OLDPWD"\C-m"' # Hint: You could also type '~-'
# FM prompt appearance
if [[ $(whoami) == 'root' ]]; then
# So that the user knows if they have root privileges:
PS1="\[\e[0;32\]mf\[m\e[m\] \[\e[0;31m\]root\[\e[m\] \[\e[0;34m\]\w \[\e[m\]\[\e[0;31m\]> \[\e[m\]"
else
PS1="\[\e[0;32\]mf\[m\e[m\] \[\e[0;34m\]\w \[\e[m\]\[\e[0;31m\]> \[\e[m\]"
fi
# Functions
# Usage
fmhelp () {
echo "hide - toggle hidden (hidden by default)
ls - lists contents of dir(s) passed in args.
lsd - list directories
cd - changed to directory \$1
cp \$@ \$2 - copies file from \$1 to \$2
mv \$@ \$2 - moves file from \$1 to \$2
rm \$@ - deletes \$@
sc \$1 \$2 - make a shortcut called \$1 pointing to \$2. If no \$2 is passed, it is evaluated as \$PWD
cpwd - copy current working directory
.., ..., .... - cd .. etc.
o \$1 - opens \$1 with xdg-open
hm - how many files are in the current directory
details - show file details (ls -lh)
fmhelp - this help menu
n - Intelligent guess of the next dir you wish to cd to. Last $1 in open, list, or makedir; last argument in copy or move; pwd before a cd
~- - BASH shortcut for \$OLDPWD
img - feh frontend with the following usage:
img -t \$2 - views the dirs/images specified in \$2..\$n as clickable thumbnails
img -s \$2 \$3 - views the images specified in \$3..\$n as a slideshow with a slide change speed of \$2 seconds
img \$@ - views the dirs/images specified
Shortkeys:
Ctrl-f - mkdir
Ctrl-h - hide
Ctrl-l - ls
Ctrl-n - cd \$n
Ctrl-o - details
Ctrl-p - cd \$OLDPWD
Ctrl-y - cpwd
Ctrl-u - clear line # urxvt default"
# Toggle display hidden files
# If $showHidden is 1, hidden files are shown
hide () {
showHidden=$(( 1 - $showHidden ))
list
# Toggle display file details
# If $showDetails is 1, file details are shown
details () {
showDetails=$(( 1 - $showDetails ))
list
# ls
listToggle () {
if [[ $showHidden == 1 && $showDetails == 1 ]]; then
ls -C --color -A -lh "$dir"
elif [[ $showHidden == 1 && $showDetails == 0 ]]; then
ls -C --color -A "$dir"
elif [[ $showHidden == 0 && $showDetails == 1 ]]; then
ls -C --color -lh "$dir"
else
ls -C --color "$dir"
fi
list () {
clear # Unclutter the screen
# List pwd if no $1
if [[ $@ == "" ]]; then
set '.'
fi
# List multiple folders:
for dir in "$@"
do
listToggle
done
n="$1" # See 'n' in fmhelp
# use feh to view thumbnails/images/slideshow
img () {
case "$1" in
-t) nohup feh --thumbnails "${@:2}" --thumb-height 120 --thumb-width 120 -S filename -d --cache-thumbnails -B black > /dev/null 2>&1 & ;;
-s) nohup feh "${@:3}" -S filename -d -B black --slideshow-delay "$2" > /dev/null 2>&1 & ;;
*) nohup feh "$@" -S filename -d -B black > /dev/null 2>&1 & ;;
esac
list
# cp
copy () {
if [[ $showHidden == 1 ]]; then
pycp --interactive --all "$@"
else
pycp --interactive "$@"
fi
list
n="${@:(-1)}" # n is the last argument (where stuff is moved to)
# mv
move () {
if [[ $showHidden == 1 ]]; then
pymv --interactive --all "$@"
else
pymv --interactive "$@"
fi
list
n="${@:(-1)}"
makedir () {
if [[ $1 == "" ]]; then
read -e n
set "$n"
fi
if mkdir -- "$1"; then
list # Update pwd to show new dir(s) that have been made.
n="$1"
fi
# rm
remove () {
rm -rfI "$@"
list
# open files
o () {
# To use xdg-open
#nohup xdg-open "$1" > /dev/null 2>&1 &
if [ -f "$1" ] ; then
case "$1" in
*.tar.bz2) tar xjf "$1" ;;
*.tar.gz) tar xzf "$1" ;;
*.bz2) bunzip2 "$1" ;;
*.rar) rar x "$1" ;;
*.gz) gunzip "$1" ;;
*.tar) tar xf "$1" ;;
*.tbz2) tar xjf "$1" ;;
*.tgz) tar xzf "$1" ;;
*.zip) unzip "$1" ;;
*.Z) uncompress "$1" ;;
*.7z) 7z x "$1" ;;
*.pdf) nohup zathura "$1" > /dev/null 2>&1 & ;;
*.html) nohup luakit "$1" > /dev/null 2>&1 & ;;
*.blend) nohup blender "$1" > /dev/null 2>&1 & ;;
*.avi) nohup mplayer "$1" ;;
*.wmv) nohup mplayer "$1" ;;
*.rmvb) nohup mplayer "$1" ;;
*.mp3) nohup urxvtc -si -sw -sh 30 -e mplayer "$1" > /dev/null 2>&1 & ;;
*.flv) nohup mplayer "$1" ;;
*.mp4) nohup mplayer "$1" ;;
*.ogg) nohup urxvt -si -sw -sh 30 -e mplayer "$1" > /dev/null 2>&1 & ;;
*.wav) nohup audacity "$1" > /dev/null 2>&1 & ;;
*.jpg) img "$1" ;;
*.jpeg) img "$1" ;;
*.JPG) img "$1" ;;
*.png) img "$1" ;;
*.gif) nohup gpicview "$1" > /dev/null 2>&1 & ;;
*) nohup urxvt -si -sw -sh 30 -e vim "$1" > /dev/null 2>&1 & ;;
esac
else
echo "'$1' is not a valid file"
fi
n="$1"
# Add shortcuts
makeShortcut () {
if [[ $2 == "" ]]; then
set $1 .
fi
echo ""$1"=\""$2"\"
alias "$1"='cd \""$2"\"'
" >> ~/.config/fm/shortcuts
source ~/.config/fm/shortcuts
# Copy pwd to clipboard
cpwd () {
echo \"$(pwd)\" | xclip
# List directories
lsd () {
ls -F "$@" | grep \/$
# Command aliases
alias mv="move"
alias sc="makeShortcut"
alias cp="copy"
alias ls="list"
alias rm="remove"
alias mkdir="makedir"
alias hm="ls -l . | egrep -c '^-'"
list # ls when fm starts
Could all of you fellow file manager-haters post your little tricks, whether just a few lines added to ~/.bashrc or fully fledged files that you source like mine?
Last edited by greenmanwitch (2011-02-07 19:58:40)

3]) wrote: once you have video files cluttered all throughout your hard drive and folders all over, thats where the 'bash' filemanager system lacks its use in terms of effectiveness.
Actually, I found this to be one of the best advantages of using bash is that it forces a user to think about file organization and making useful naming schemes for files.
For example, instead of having 1000+ media files in one directory I subcategorize theme by genre or whatever, and then probably subcategorize them again.
Then I usually rename the files to something meaningful, like if I have 50 pictures of my kids birthday, just do a for each loop on the directory and rename all the files donovan_birthdayX.jpg where X is an integer incrementation.
essentially. just don't "have files cluttered all throughout you hard drive and folders all over". and your life will be much happier regardless of how you manage your files.

Set midnight commander as default file manager.

How can i set mc as a default file manager to open files from chrome downloads in it?
I've put a .desktop file inside /ust/share/applications/
midnight-commander.desktop
[Desktop Entry]
Name=Midnight Commander
Type=Application
Terminal=true
Comment=A visual file manager
Exec=mc
TryExec=mc
Icon=MidnightCommander
Categories=System;FileTools;FileManager;
and run xdg-mime default midnight-commander.desktop inode/directory. But when i try to open something from chrome downloads nothing happens.

anonymous_user wrote:You set "Terminal=true", but what terminal is it trying to run? Do you have xterm installed?
I'm using zsh + urxvt. Xterm is also installed
Last edited by innocent_rifle (2013-01-10 12:26:54)

Bash CDE file manager problem

I have the following problem:
I use the CDE and the bash shell. If I start a bash terminal from the file manager file menu, the environment variables are not set correctly. The entries made in the file /etc/profile are just ignored.
However, the following works correctly:
-if I start the bash terminal from the CDE toolbar
or
-if I use the bourne shell (both variants file manager and CDE toolbar work)
It seems that the file manager is not receiving the correct environment information from the CDE.
Thanks for any help.

Hi,
Try this patch for this issue.
Patch id : 109166-11
Download this patch from http://access1.sun.com or http://sunsolve.sun.com
Let me know the result.
Thanks,
Senthilkumar
Technical Support Engineer
Developer Technical Support
Sun Microsystems, Inc.
http://www.sun.com/developers/support

How to use "choose file with prompt" command?

I need to use "choose file with prompt" command and I want give user possibility choose ONLY images (jpeg, png, gif). So, I write like this:
choose file with prompt "Please, choose images for processing..." of type {"JPEG Image"}
But this doesn't work! - All files (including jpegs) are dimmed, and user can't choose any....
So, how can I filter JPEGs, PNGs and GIFs?

I have found, that most of images on my computer has missing file_type, I don't know why..... so "type identifier of (info for (choose file))" also doesn't work properly.
The only one way that 100% works is use Uniform Type Identifier (UTI) -- details here: http://www.huw.id.au/code/fileTypeIDs.html
thanks.
iMac G3, PowerBook G3 FW Mac OS X (10.4.5)

KDE file manager UI fonts impossibly tiny (RESOLVED)

The KDE installation seems to be at variance with documentation on kde.org.
I can not find many of the configuration files named at kde.org.
My problem is that while I can change fonts in the file display window of file manager, the font in the menu bars and left side tree are barely readable.
This is more severe in the superuser file manager than in the user version, but I'm at a loss in changing either one of them.
My screen is set at 800x600.
I have been thru the files at /root/.kde/share/config.
All help appreciated.
Bill Barnes

Thank you.
I have been all over kcontrol, but found that to do what I wanted was to invoke it in a superuser terminal. That did it.

Permz - Quickly change file permissions in any file manager

Designed to be integrated into any file manager, permz is a bash script which presents a GUI menu. You can use it to quickly change file permissions and ownership as a normal user or as root, and delete files as root. I wrote this because I have yet to see a file manager that isn't cumbersome for this - the mechanism is usually buried on a second tab of the Properties window, and changing permissions often involves multiple clicks in a grid. To change the owner of a file, you need to type the username. And if the file is owned by root, you can't do anything.
permz --help
Presents a GUI menu for changing file permissions/ownership. May be run
as a normal user or root.
Requires: zenity gksu
Optional: sudo (recommended to prevent multiple root password prompts)
Usage: permz FILE [...]
MENU FUNCTIONS:
rwxrwxrwx Sets file(s) to given permissions
Sticky Clear/Set Performs "chmod -t" or +t to clear or set the sticky
bit. You may select to clear/set sticky in addition
to changing other permissions.
Recursive go-rxw "chmod -R go-rxw" on file(s) recursively, denying
access to non-owners
Recursive go-w "chmod -R go-w" on file(s) recursively, denying write
to non-owners
Recursive ugo+rX "chmod -R ugo+rX" giving read access to all. Also
sets +x for directories and executables.
Recursive ugo+w "chmod -R ugo+w" on file(s), giving write to all
(You may select several compatible recursive functions above at once)
Owner USER As ROOT Sets ownership to USER:USER as root
DELETE As ROOT Deletes file(s) as root. Must be used alone or with
"Perform Recursively" (to delete directories - USE
WITH CAUTION). Not available if permz is run as root.
Perform As ROOT Run as root to change selected permissions.
(Use of root is automatic when changing ownership)
Perform Recursively Adds -R to all chmod, chown, and delete commands to
descend into subdirectories. Use in conjunction with
any other functions. (Recursion is automatic for
"Recursive" functions above)
Current su command is set to: gksu -gS
If you're somewhat familiar with bash, adding additional options or changing the existing ones is straightforward.
I have tested it pretty thoroughly but if you do encounter anything amiss please let me know.
More details at http://igurublog.wordpress.com/downloads/script-permz/
And in the AUR at http://aur.archlinux.org/packages.php?ID=36978
Instructions for integrating permz into PCManFM-Mod are here.
Last edited by IgnorantGuru (2010-05-05 13:53:08)

rransom wrote:Recursive ugo+rX would be more useful than "Recursive ugo+r (dirs +x)". (The +X feature of chmod is available at least in GNU coreutils, FreeBSD, and POSIX 2003.)
Done - thanks for the tip. I also left the old code active in there with just the menu option disabled, so if anyone wants it the other way or wants both it's easy to enable. The difference is that the old way won't make any files +x, just dirs.
permz doesn't provide every possible setting of permissions, just common ones, so you may want to customize it. But I used to have these as user actions when I used Krusader and I found these were the handy ones, at least for me.

Can't open file - file manager error

I can't open a couple files I was working on this afternoon. I shut down my computer when I left the office, now that I've booted again, when I try to open either of these 2 files I can a message that says "While attempting to access "file name" the file manager reported an error - 39."
I haven't made backups of these files, so that isn't an option.
I've rebooted a couple times, I've repaired disk permissions, but nothing works.
Previous files I worked on DO open correctly.
HELP! PLEASE!

I'm not sure if you have time to hold the hand of a "newbie" to Terminal
Of course! I'm always happy to introduce people to the command line
1) prompt$ - is my name bryceinman$
Most likely, yes. The default prompt usually contains the machine name, and sometimes the folder you are sitting in, and will usually end with a $ or a % (for a normal user), and typically a # for the root user.
2) cd - is that the name of the hard drive or do I just type "cd"
That is a command which means "c"hange "d"irectory (when you hear "directory", think "folder") and is how you move from one directory to another from the command line.
3) after that, it appears that I'm simply typing the path to the location of the file.
Yep.
Are you saying the "filename" will be the next string displayed by Terminal if, indeed, the file can >be found correctly? (Right now I'm getting the following: -bash: Macintosh: command not found)
That's correct. Once you've changed directories to the directory/folder that contains your problem file, you type at the prompt "ls -l filename", except that you will substitute the real file name for the word "filename" in my example.
And yes, using this same logic, the "cat filename > /dev/null" you will use the actual file name in place of "filename".
Maybe an example will help. Let's say I have a machine named tomservo, and a file called SmithDoc.txt, and it's located in my Documents folder, in a sub-folder called Work. To perform my above suggestions from the command line, I would do the following (I also show example output):
(Launch Terminal from Applications->Utilities)
tomservo$ cd Documents/Work
tomservo$
tomservo$ ls -l SmithDoc.txt
-rw-r--r-- 1 glsmith staff 512 Jun 10 22:01 SmithDoc.txt
tomservo$ cat SmithDoc.txt > /dev/null
tomservo$
A few things to note here. Since I added example output to the above steps, you may wonder why there is a blank prompt after the "cd" and the "cat" steps. This is normal Unix behavior. Many times, commands will not print out anything if they operated correctly. So, since I was able to change directories correctly in the first step, I got no output. In the second step, I'm asking the system to print information about the file ("ls" means "list", think "dir" in Windows), so that's why we see output. In the third step, I'm asking the system to read the file ("cat" means "concatenate"), but to redirect the output to the system bit-bucket (/dev/null). Don't worry too much about what /dev/null is -- think of it as a black hole. Anyway, since all the output is going there, that's why we don't see any output there either.
Why do I want to do this? Well, since "cat" will read the file without caring about what application created it, it's a good way to test the file's integrity in the filesystem itself. If there is something wrong with this file, the "cat" will get throw an error.
One last thing to mention, and hopefully this won't confuse the matter. If you have a file that doesn't have spaces in its name, please use that one to test with. That's why I used SmithDoc.txt. The command line can certainly interpret files with spaces in the name, but you must enclose the filename in quotation marks, or escape the space (don't worry about what that means). So, if my filename was actually Smith Doc.txt, anytime I typed this on the command line, I'd have to do:
prompt$ ls -l "Smith Doc.txt"
and
prompt$ cat "Smith Doc.txt" > /dev/null
Hopefully this all makes sense!

Yosemite is awful- unable to empty trash, volume options are haywire, error codes on file management, and files won't replace when moved. What are my options at this point?

Like the topic - "Yosemite is awful- unable to empty trash, volume options are haywire, error codes on file management, and files won't replace when moved. What are my options at this point?"
I installed this OS, and it looks nice, but it's terrible to use. I randomly have the volume controls get disabled, and sometimes the volume menu in the system tray does nothing when adjusted which I've never seen in an OS before. The trash won't empty. When I try to drag and drop newer files over existing ones, nothing happens. The old ones just stay there. I have to delete the old ones and then move the new ones. And when I go into the protected files to manage audio plugins (I make music), the first thing I hit are error codes galore, and password prompts that either don't popup when they should, or don't execute the command after I provide my password.
What can I do now that I installed the flames of **** onto my computer?

Back up all data before proceeding.
This procedure will unlock all your user files (not system files) and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.
Step 1
If you have more than one user, and the one in question is not an administrator, then go to Step 2.
Triple-click anywhere in the following line on this page to select it:
sudo find ~ $TMPDIR.. -exec chflags -h nouchg,nouappnd,noschg,nosappnd {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window by pressing command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1, if you prefer not to take it, or if it doesn't solve the problem.
Start up in Recovery mode. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open. In that window, type this:
resetp
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Thunar as default file manager

Hi, i've installed today kdemod and now the default file manager in gnome is konqueror. I used thunar and i want to put it back to default file manager. I've found this tuturial but i can't execute the command sudo. i've already add my user trought visudo but i doesn't apear on /etc/sudoers so when i try to run sudo when it asks me the password even if I put the root password it doesn't allow me to execute the command.. Any sugestion to solve the problems?? I really want to get back thunar to default manager.
cumps

What is your user name and the output of cat /etc/sudoers ?
With sudo you should use your user password not your root password
You can also use the "su" command built-in linux,
typing "su" or "su root" prompt a root password query dialog and then gives you a root terminal
sudo is a mean to gain root privilege that's all, you can follow the tuto without it.
Edit : I haven't see that actually sudo is called in the scripts
you can edit the script removing calls to sudo. and run them as root
the part with aptitude is ubuntu specific, it's their package manager like pacman is ours
so adapt the command accordingly
Also maybe archlinux doesn't put gnome .desktop like ubuntu
use the locate command to find it
example "locate nautilus" or "locate nautilus |grep /usr/share" (to limit the result to /usr/share if you have too much result)
if you had just installed something and want to look for it don't forget to run "updatedb" beforehand
Last edited by ChoK (2008-10-24 21:24:29)

Pyfmii - nine panel wmii/mc-like file manager

pyfmii - git repository
AUR: http://aur.archlinux.org/packages.php?ID=25148
Git Source: git clone git://github.com/Procyon2/pyfmii.git
A file manager with nine panels with the looks of wmii and behavior of mc
Dependencies: python
Screenshots:
Features:
- Nine panels
- Colorize by extension
- Command box that runs everything in a shell
- Tab-completion in command box
- While command box is up browse around and add items with alt+enter
- Command box pops up as soon as you start typing
- Customizable with ini-like rc file: ~/.pyfmiirc
- Multi session history (alt+p, alt+n): ~/.pyfmii_history
Usage:
./pyfmii -h
./pyfmii [ACTIVEPAD [OPENPADS]] [DIRECTORIES]
Default: ./pyfmii 1 . ~ ~ ~ ~ ~ ~ ~ ~
e.g.: ./pyfmii 2 1 9 /usr/bin ~/bin
will have panels 1 2 9 open with 2 active and 1 = /usr/bin, 2 = ~/bin, 3 = ~, 4 = ~ etc
Keybindings are on the git site
Bugs:
Recently/probably fixed bug:
- Restoring keypad mode in command win after resizing
- Files with macros work
- Opening vim in pyfmii and resizing gives an EINTR that will now be ignored.
- Resizing to a really small window caused a crash/infinite loop
Different behavior/features that I won't change:
- if with tab-completion you have a full match and there are more matches it will behave as if there was just a full match
- e.g.: dirs: "aa, aab" type: "aa<TAB>" -> "aa/"
- F2 advanced menu is not context sensitive like mc's
- you can't browse search results from '/'
- no bookmarks, ^\ will quit python actually
- F2-@ doesn't put the cursor at the start, F7/mkdir doesn't add a space so you can't begin typing right away
- mark all items marks directories too
- cd'ing to symlinks is like cd'ing to the actual file, unlike in bash/mc. I don't think this can be fixed in python
Last edited by Procyon (2009-04-06 20:07:33)

I just realized that alt+1-9 is commonly used in WMs, am I right? And the same for Alt+F1-F9
CTRL+1-9 doesn't seem possible because CTRL+1 = 1 and CTRL+4=^\ which, as I said before, immediately quits python.
CTRL+F1-F9 is possible. I had previously bound ^F5-^F8 to a no-confirm version.
Shift+F1-F9 is also possible
EDIT:
There is a mismatch:
Xterm Shift+F1 = F13
URxvt Shift+F1 = F11
/EDIT
EDIT: that leaves CTRL+F1-F9. I will remove all no-confirm keys. I have also put the command of F5-F8 in the configuration file so having two versions is not necessary (this will be in the next git push)
BTW Alt+1-9 (and now CTRL+F1-9) is used for setting the selected dir in the panel of the number (or cwd if a file), and it is also used in the command box to change panels (like regular 1-9) (after all you want "1-9" and "!-(" for commands)
And I noticed that the unicode space does not just not work on VC but also any non-unicode term like aterm. A normal space does work in all except in screen where it will cut off. If you go to the next window and back the bar restores, but any movement will cut it off again. Maybe there's a setting in screen that can control it. For now I removed all hardcoded unicode.
EDIT:
Screen behaves differently with "bce on" and "bce off",
off -> the long selector line is not drawn at all
on -> the long selector line is only drawn after refresh, and disappears when changing selection
/EDIT
aterm also seems to not work with curs_set(2) but it does with 1 and that is the same for everything (maybe not VC, haven't tried).
EDIT:
Config changed
If you made no changes you can remove it to let pyfmii autogenerate one, or add the following to ~/.pyfmiirc:
[basic]
#F5
copy = :cp -R -v -i -- %t %D
#F6
move = :mv -v -i -- %u %D
#F7
mkdir = :mkdir -p -v
#F8
remove = :rm -R -v -I -- %u
EDIT:
Besides Ctrl-F1-F9, I have also made F1-F9 have the same behavior in the command box.
Last edited by Procyon (2009-01-29 13:58:50)

Clex file manager of AUR not installing properly

I used yourt to install 'clex' file manager from AUR. It installed without any problem but on running the command 'clex' there was a message that 'cfg-clex' need to be run first. I did that and again ran clex. Not only did it crash but after termination, garbage characters continued to appear on the command prompt of the terminal. It was very scary, reminiscent of computer viruses, and very unusual for otherwise very smooth and stable archlinux system. On closing the terminal, uninstalling clex and rebooting, the system seems to be working all right. Is there a problem with the package or there is some problem in my setup/installation procedure?
Last edited by rnarch (2012-11-28 04:56:00)

tomk wrote:FYI it builds and works fine here, so the only conclusion is that it was some issue with your system.
I picked up courage and installed again but with same results. Here is the screenshot:
http://i.imgur.com/GB9Bq.png
The command 'clex' produces output of some numbers and lib file names as shown in the screenshot. The program would then terminate with 'Aborted'. After this, any clicking of left or right mouse buttons or turning of the mouse wheel would produce garbage at the command prompt. Typing reset (as suggested by jwbirdsong above) would restore the screen to normal state with no further problem with mouse etc. The whole thing is reproducible and seems harmless (can be used for entertainment of kids if not corrected!). Any help to correct this problem will be appreciated. I could not find any (relevant) links to this problem on searching forum, wiki or google.
Last edited by rnarch (2012-11-28 12:41:29)

Some videos are semi-missing - they do not show up in File Manager apps or another app

I have what I will call three FILER apps: File Browser, Air Browser and File Commander. I also have MovieSRTPlayer. Those apps appear to not register the presence of some video files that I have definitely copied to my PB. The MovieSRTPlayer will overlay a .srt file's text over a video allowing the pb to show subtitles. It works as long as it can find the video and srt files.
I am definitely transferring a series of video files to the pb's video folder. I am also transferring a companion file to that folder. The companion file is a subtitle file in the form of an .SRT file.
THREE file manager type apps do NOT show those files as present in the video folder. The Video app itself does show and play those video files.
I have copied the files using both wifi-sharing and when they did not show up that way, I copied them using the usb cable to the pb's Z: drive and the video folder.
As stated the dam! files play in the video app. But they do not appear in the various filer apps. And they also do not show in another app, one that will display the subtitle (.srt file) file overlaying the video. In all instances it is as if the pb does not register the presence of those files on the pb.
Now, what is interesting is that when this first cropped up, 7 files were missing - just a mix of video (no .srt files involved). That is they showed in the video app and played but the filer programs did not show them. I managed last night and this morning to get 7 of those to finally show by copying/moving/deleting and recopying. But now I'm running into this brick wall again. I have repeatedly copied two video (avi files) and their companion .srt files to the video folder. They are in that folder (I've looked using usb and wifi-sharing) and they play in the PB's video app. They are most certainly on my pb.
Oh, and yes, I've rebooted a number of times.
Ideas?

I have what I call 3 file manager apps. File Browser, Air Browser and File Commander (the older free version).
They all show or don't show the same thing. So files are missing. And SIZE is not the sole determining factor. When I was testing MovieSRT and "lost" some files I copied and renamed avi and .srt files. So there are two extra .srt files in the Video folder. But while they are 32kb (kilobytes) and 58kb respectively, they do NOT show up in the File managers. The other two identical files with the names matching the .avi files do show up. The one very large mp4 (2gb) does not show up. A subfolder I created just as a test does not show up. But the large mp4 and subfolder were showing up while I was actively copying the 2gb file - they would show up as the file was being copied - the filemanagers showed the file getting larger and larger and while doing so the "missing" subfolder also kept showing up. Then once the large file was completely copied, both it and the subfolder "disappeared" - again, the large mp4 does show in the Video app and it plays.
My persistence probably is based on the fact I was a computer programmer many eons ago! Also, I was trying to get YOUR app to work and the avi files were not showing up in your listing but they were showing and playing in Video app (but no subtitles). Finally, after copying/moving/re-copying over and over including moving and copying to the PB's Print folder (just since it was empty) and copying it back to the video folder (now 2 copies), the files would finally show up. Peculiar - yup!
Oh, one other thing - the 3 file managers all show what I will call the virtual Playbook-Demo video in their listings - your app does NOT show it. Obviously, it is not located in the Video Folder but somewhere in the bowels of the PB. So, the filemanagers are relying on some "file structure" that is not fully correct. But your app does not appear to show it.

Changing the default file manager in XFCE

How would I go about using Nautilus as the default file manager in XFCE instead of Thunar? I know it can be started up with 'nautilus --no-desktop', but how do I make this the default when opening folders from the desktop, menus, etc..?
The main reason I want to do this is because Thunar doesn't seem to remember a folders last setting. For example, there are folders which I would like to permanently view as a list, sorted by date; but there are plenty of other folders where this is not suitable. Nautilus remembers settings for each folder, Thunar doesn't, and it gets annoying changing the view mode each time. Also network browsing is easier in Nautilus, and I also like the way it tells you how fast file transfers are going.
Thanks very much,

Well, it might be considered a dirty hack but it has worked for me in gnome before so it should also work in xfce. Just edit the thunar.desktop file in /usr/share/applications and replace the Exec=thunar to Exec=nautilus --no-desktop and save the file. Then any time thunar is launched, nautilus will be launched instead.
Otherwise, you can edit the menu with the menu editor and change the File manager command and do the same in the panel icon properties. Both methods will work.

Is there any downside to using a reference type library if I use Time Capsule and will do file management only from within Aperture?

Have done a lot of reading to get prepared to convert to Aperture 3 and have this question regarding setting up my library type.
I'm not a professional -just a heavy user hobbyist.
It appears that the major factors in using reference style is to backup the images with Time Capsule and always do moves or deletes from within the Aperture application.
If my architecture matters here's what I have that may be involved in photo management and editing:
iMac (latest 27" high power version with lots of memory)
Internal 2TB HD where the library is stored
External (FireWire) 2TB HD where the images are stored
External (FireWire) 6TB HD backup drive
In the future an iPad for remote work on images (when/if available) and a Mac laptop (for same remote use)
I see major downside issues to letting the library manage my files - such as inaccessibility (or awkward accessibility) to the images for other programs, and performance issues when the library gets large (thousands of images or 100+ gb in size)
The chief complaints I've seen regarding using a reference mode is the broken link issues created if file management is done outside of Aperture (adds, deletes, moves of files) and the inability to use the Vault function for backup.
One feature that I imagine I'd like to have is maximum integration with Final Cut Pro X and that's one area I haven't seen much on and would be interested to hear about if that integration is affected with the choice of managed vs referenced library types. (I like to produce film clips that are combinations of pics and video and want to be set up so that is done in the easiest fashion when working in FCP X)
I'm sure I've not seen all sides of this issue and would like to see some discussion around this question.
Thanks to everyone contributing!
Craig

Goody, Goody, you hit a few of my favorite subjects! Herewith some comments, with the usual caveats - true to the best of my knowledge and experience, others may have different results, YMMV, and I could be wrong.
I run Aperture on two machines:
-- 2007 Mac Pro with 2x2.66 GHz Xeon, 21 GB of RAM, a 5770 GPU, and multiple HD. I have about 11,000 images, taking up 150 GB. (Many are 100 MB TIFF, scanned slides)
-- 2006 Mac Book Pro with 1 2.0 GHz Core Duo, 2 GB of RAM and a 240 GB SSD.
Two very different machines.
-- Aperture Libraries are all the same - Managed or Referenced. If Managed, then the Master image files are inside the Package, if Referenced, they are outside, and you can have any combination you want. Managed is easier, but Referenced is not hard if you are the least bit careful.
-- While the sheer size of an Aperture Library is not a big issue, the location on disk of the different components can have a tremendous impact on performance.
-- Solid State Drives (SSD) read and write faster than regular Hard Disks (HD) and, what is more important, empty HD read and write much faster than full HD.
-- Aperture speed requires a combination of RAM, CPU, graphics processing unit (GPU) speed, and disk speed. The more RAM you have, the less paging you will see. With enough RAM, the next bottle neck is CPU (speed and cores) and GPU speed. But even then you will still have to fetch an image (longer if you pull the full resolution Master, read and rewrite the Version file, and update the Preview and Thumbs.
So what works?
-- RAM, RAM, and more RAM. 4 GB will work, but you will page a bit. 8 GB is much faster. On my old MacPro the sweet spot was about 16 GB of RAM.
-- Keep your Library on your fastest (usually internal) drive. Keep that disk as unloaded as possible. How do you keep it unloaded? Either buy BIG, 1 TB+ or move your Masters off onto another disk. The good news here is that as Master files are written only once and never rewritten, speed of this disk, as opposed to the disk that holds the Library, is not important. There is a one second pause as the Master is read into memory and, if you have enough RAM, that is it - the Master will never be paged out. If, on the other hand, you do not have enough RAM, and you do a lot of adjusting at full resolution, then the speed of the disk that holds your Masters will become very important due to paging.
-- I found that I picked up a tiny bit of speed by keeping the Masters on a dedicated disk. Thus, in your configuration, if you can dedicate that 2 TB FW HD to your Masters, you should see very nice performance.
Final notes on backups and archives:
-- One conventional wisdom is that you should make an archive copy of every image file before or as you load them into your system. (Aperture in this case.) This archive is then never touched or deleted.
-- An alternative approach is that you do not keep such an archive, but only the images that you have in your Aperture Library. And when you delete from the Library, you no longer keep a copy anywhere.
I do the following:
-- Card to Aperture. Card is then kept at least 24 hours until all of my backups have run. (I use three - Time Machine, Clone, and off site.)
-- I do not keep archive copies. If I decide to delete a file, my only recourse is to recover it from Time Machine during the six month cycle of my Time Machine backups. Thereafter, it is lost.
There are merits to both approaches.
Hope this is clear, correct, and responsive to your needs.
DiploStrat

Prompt Command File Manager: tiny bash FM

Similar Messages

Maybe you are looking for