Ticket #1493 (assigned enhancement)

Opened 9 years ago

Last modified 4 months ago

#sh should start in the user's remote home dir, consistently with rsh/ssh

Reported by: narcan Owned by:
Priority: minor Milestone: Future Releases
Component: mc-vfs Version: master
Keywords: Cc: zaytsev, mcepl@…
Blocked By: Blocking:
Branch state: no branch Votes for changeset:

Description

Hello,
I think its a good idea.

Vassilii Khachaturov wrote:
"The default behaviour of the shell link virtual file system should
probably be consistent with the rsh/ssh programs behavior --
initially changing not to the remote filesystem root, but rather
to the remote home directory."

Original message:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276878

regards

Denis Briand

Change History

comment:1 Changed 9 years ago by slavazanko

Hm... usually home dir placed by '/home/<user>' template. But may be placed in any other (such as /home/m/martines).

What do in this case? Be read /etc/passwd or if no homedir in default place, then open root of fs?

And, of course, need to be optional. :) Because this will change default behavior - someone will unhappy.

comment:2 Changed 9 years ago by slyfox

  • Owner set to slyfox
  • Status changed from new to accepted

comment:3 Changed 9 years ago by slyfox

Sorry, too many mostly useless options is not a good idea

We _could_ slightly change the meaning of a fish url. For example:

/#sh:127.0.0.1 will lead to chdir to $HOME
and
/#sh:127.0.0.1/ will lead to chdir to /

comment:4 follow-up: ↓ 5 Changed 9 years ago by ossi

that's too magic.
i think an explicit use of ~ would be ok. in particular, this way it would be consistent for nested locations inside the home dir:

/#sh:localhost/~/stuff

anyway, you should investigate prior art (well, derived art, by all practical means, but still "they" are ahead of mc now): kde's kio (maybe have a look at krusader) and gnome's gvfs. in fact, you should try to get the ball rolling regarding a unified VFS scheme - xdg@….

comment:5 in reply to: ↑ 4 Changed 9 years ago by slyfox

Replying to ossi:

that's too magic.
i think an explicit use of ~ would be ok. in particular, this way it would be consistent for nested locations inside the home dir:

/#sh:localhost/~/stuff

Yep you are right. '~' is more usable and simpler to implement on VFS layer (w/o hacks in higher layers)

anyway, you should investigate prior art (well, derived art, by all practical means, but still "they" are ahead of mc now): kde's kio (maybe have a look at krusader) and gnome's gvfs. in fact, you should try to get the ball rolling regarding a unified VFS scheme - xdg@….

Thanks. We are thinking about using GIO/GVFS, but noone tried to play with it yet.

comment:6 Changed 8 years ago by zaytsev

  • Cc zaytsev added
  • Version changed from 4.7.0-pre1 to master

comment:7 Changed 8 years ago by angel_il

~ is bashism and cd ~ dont work in sh

comment:8 Changed 8 years ago by zaytsev

Ilya, wanna have a go at it? Sounds sweet to implement it for 4.7.5.

comment:9 Changed 7 years ago by andrew_b

  • Branch state set to no branch
  • Milestone changed from 4.7 to Future Releases

comment:10 Changed 23 months ago by andrew_b

  • Status changed from accepted to assigned
  • Owner slyfox deleted

comment:11 Changed 4 months ago by mcepl

  • Cc mcepl@… added
Note: See TracTickets for help on using tickets.