about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* core.actions: fixed cm/ca keyshut2012-11-091-1/+2
|
* widgets.browserview: catch an error in _draw_bordershut2012-11-051-5/+8
|
* Makefile: use python2.7 toohut2012-10-181-1/+1
|
* gui.ansi: Fix crash https://savannah.nongnu.org/bugs/?37346hut2012-10-031-0/+3
|
* Revert "config/rifle.conf: Fix handling of mkv files"hut2012-08-201-13/+0
| | | | | | | This reverts commit 14412eea0cd7ec556062f8f984dc5577ebdc8b30. Since rifle now does file-extension-based file type recognition, this commit is not necessary anymore.
* ext.rifle: Use python mimetypes module again, file as fallback.hut2012-08-201-4/+21
| | | | | | | | | file is unreliable, often simple file-extension based recognition yields better results. See: https://github.com/hut/ranger/issues/44 https://bbs.archlinux.org/viewtopic.php?pid=1147719#p1147719
* ext.rifle: Fixed rifle when running as standalone programhut2012-08-161-1/+1
|
* Revert "core.runner: removed 's', 'p', 'w' flags to behave like rifle"hut2012-08-151-1/+19
| | | | | | This reverts commit d6c78470ba0e3a9923d5cc13a5babaca4d52aecf. It makes ... little sense atm to remove this.
* core.loader: implemented progressbar for CopyLoaderhut2012-08-152-3/+28
|
* core.actions: move paste() logic to core.loader.CopyLoaderhut2012-08-152-51/+52
|
* core.actions: update shutil_g paste function to not use Environmenthut2012-08-151-8/+8
|
* core.actions: imported shutil_g paste function from v1.2.3hut2012-08-153-34/+364
| | | | | | | | | | | | | | | | | | | | | The code implements the functionality of cp and mv coreutils in python and was removed as of v1.4.0 for efficiency and simplicity reasons. I moved it back in for several reasons: 1. I plan to enhance shutil_g to report on its copying status so I can display a progress bar 2. With no need for external cp/mv programs, distribution-specific differences (like broken backup option on MacOS/BSD?) become irrelevant 3. You can still copy in ranger if you accidently delete /bin/cp 4. It gets rid of the occasional bug that the cp process keeps running when ranger is terminated while copying The possible downside is reduced efficiency in copying and ranger might get stuck if the copying function is blocked. Let's see if it works out.
* core.runner: Added TODO: "make 'r' flag work with pipes"hut2012-08-151-0/+1
|
* config/rifle.conf: added note about 'c' flaghut2012-08-151-0/+2
|
* core.runner: removed 's', 'p', 'w' flags to behave like riflehut2012-08-151-19/+1
| | | | | | | | instead of 's', you can append &>/dev/null instead of 'p', you can append |less instead of 'w', you can append ;read If there is demand, I'll add the flags back in.
* ext.rifle: add TODO entry "Test all of the hooks properly"hut2012-08-151-0/+1
|
* core.runner: fixed missing importhut2012-08-151-0/+1
|
* ext.rifle: removed bad importhut2012-08-151-1/+0
|
* core.runner: remove 'setsid' dependency, use Popen_forkedhut2012-08-151-5/+8
|
* ext.popen_forked: tweak mechanismhut2012-08-152-24/+22
|
* ext.rifle: added some commentshut2012-08-151-0/+3
|
* ext.popen_forked: separated Popen_forked to a libraryhut2012-08-152-14/+47
|
* core.runner: renamed flag "d" to "f" in the runner toohut2012-08-152-8/+8
|
* ranger.__init__: print python info with --versionhut2012-08-151-1/+2
|
* widgets.browsercolumn: Catch a "wmove() returned ERR" exceptionhut2012-08-141-1/+4
|
* config/rifle.conf: added notehut2012-08-141-0/+2
|
* ranger.__init__: cleaner ranger.log()hut2012-08-141-4/+4
|
* deleted colorschemes/default88.py, it is outdated (and ugly)hut2012-08-131-45/+0
|
* colorschemes.snow: updated to work with progressbars and taskviewhut2012-08-121-3/+12
|
* colorschemes.jungle: changed progressbar color to greenhut2012-08-121-0/+1
|
* colorschemes.default: changed color of progressbar to bluehut2012-08-121-3/+5
|
* widgets.statusbar: draw an averaging progress barhut2012-08-127-4/+32
|
* config/rifle.conf: added chromiumhut2012-08-121-0/+1
|
* ext.rifle: BSD-friendly setsid usagehut2012-08-111-8/+15
|
* ext.rifle: remove unused _apply_flags methodhut2012-08-111-28/+2
|
* Merge branch 'stable'hut2012-08-105-3/+8
|\ | | | | | | | | | | Conflicts: doc/ranger.1 ranger/defaults/apps.py
| * ceci n'est pas un nouveau version v1.5.5hut2012-08-104-4/+7
| |
| * defaults/apps.py: added "odb" entryhut2012-08-101-1/+1
| |
| * core.runner: use setsid to stabilize detached programshut2012-08-091-0/+2
| | | | | | | | | | | | This fixes the bug that some programs are killed even if they were run with the "d" flag, if ranger is killed by closing its terminal with the window manager instead of closed with :quit.
* | config/rifle.conf: added "odb" entryhut2012-08-101-5/+5
| |
* | gui.ui: Amendment to previous commithut2012-08-091-1/+0
| |
* | gui.ui: Fixed crash due to bad ui.termsize with padding_right=Falsehut2012-08-091-1/+1
| | | | | | | | https://bbs.archlinux.org/viewtopic.php?pid=1143920#p1143920
* | ext.rifle: silenced output of forked programshut2012-08-091-2/+7
| |
* | ext.rifle: flags now work with commands with pipes, semicolons etchut2012-08-092-7/+21
| | | | | | | | | | | | | | | | rough explanation: before, the "t" flag would run the program in a terminal by prepending something like "xterm -e " to the command. If the command is "ls | less", it would result in "xterm -e ls | less". This commit changes it so the result looks more like "xterm -e sh -c 'ls | less'" and works as intended.
* | ext.rifle: fix "flag r" in rifle.confhut2012-08-081-0/+1
| |
* | widgets.browsercolumn: Fixed segmentation fault due to 93601b17hut2012-08-081-5/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://github.com/hut/ranger/issues/45 hut: I've been experiencing irregular segfaults in ranger-master for which I can't figure out the reasons. Here is all the info I got: - It started around the time of commit 5417dda - I think it is a problem with curses' addstr/addnstr function - It happens randomly, there is no specific action that causes it - It happens more often with python3 than with python2 - It's most likely somewhere in here: git diff master 5417dda5^ ranger/gui/widgets/browsercolumn.py - but I don't see anything wrong. hut: I nailed it down to 93601b1 and fixed it. For what it's worth, this is how to reproduce it: (tested with rxvt-unicode 9.15 and dwm but may work with any other tiling window manager): - Ensure that the setting display_tags_in_all_columns is set to True (this is the default) - Tag a file or directory with the "t" key - Navigate so that this tagged file is the LAST file you see of a column other the main column - Open a new window (resulting in rangers window getting smaller by at least one row) - Close a window (resulting in rangers window growing back to the original size) - Watch rangers brain being splattered all over the sand If you don't use a tiling window manager, you can do steps 1-3 and then resize rangers window very quickly. When resizing ranger manually, one of these messages is printed instead of "Segmentation Fault": - *** glibc detected *** python2.7: corrupted double-linked list: 0x0949cc98 *** - python2.7: malloc.c:3964: _int_free: Assertion `nextchunk->fd_nextsize->bk_nextsize == nextchunk' failed.
* | core.tab: fixed restoring pointer on tab changehut2012-08-072-3/+5
| |
* | config/rifle.conf: Fix handling of mkv fileshut2012-08-071-0/+13
| | | | | | | | | | | | | | | | | | https://github.com/hut/ranger/issues/44#issuecomment-7558251 adam8157: have 10 mkv files, four of them are "application/octet-stream"(and file without options returns "EBML file, creator matroska"), others are "video/x-matroska".
* | widgets.taskview: show progressbar only if task supports ithut2012-08-072-5/+9
| |
* | widgets.taskview: added progressbars for dir loading taskshut2012-08-075-2/+14
| |
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-02 16:10:20 +0000