On Tue, 2013-07-09 at 22:13 -0400, david...@ling.ohio-state.edu wrote:
> i would expect
>
> $ HOME=/mnt/music gedit
>
> to do what you want.
And you are right :). Thank you!
$ echo $HOME
/home/rocketmouse
$ HOME=/mnt/music gedit
$ echo $HOME
/home/rocketmouse
$ ls -hAl /mnt/music/ | grep
hi ralf.
On Tue, 9 Jul 2013, Ralf Mardorf wrote:
On Tue, 2013-07-09 at 04:44 -0400, shawn wilson wrote:
You could probably do:
su -l $USER HOME=$HOME/$app $app
Hi Shawn,
that's great, thank you very much! I can add this to my next audio
session scripts, so no searching for hidden configs an
On 07/09/2013 03:53 PM, ha wrote:
On 07/09/2013 12:24 PM, Ralf Mardorf wrote:
su -l $USER HOME=$HOME/$app $app
...
[rocketmouse@archlinux ~]$ su -l $USER HOME=/mnt/music/ gedit
Am I reading this correctly? Shouldn't it be:
su -l $USER HOME=/mnt/music/gedit gedit
No. This doesn't make sense
On 07/09/2013 12:24 PM, Ralf Mardorf wrote:
su -l $USER HOME=$HOME/$app $app
...
[rocketmouse@archlinux ~]$ su -l $USER HOME=/mnt/music/ gedit
Am I reading this correctly? Shouldn't it be:
su -l $USER HOME=/mnt/music/gedit gedit
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.o
On Tue, 2013-07-09 at 04:44 -0400, shawn wilson wrote:
> You could probably do:
> su -l $USER HOME=$HOME/$app $app
Hi Shawn,
that's great, thank you very much! I can add this to my next audio
session scripts, so no searching for hidden configs anymore, for apps
that don't allow to set a path by t
You could probably do:
su -l $USER HOME=$HOME/$app $app
(untested)
Also maybe see about wrapping what you need (probably tons of app specific
mojo) around fakeroot or even use fakeroot and schroot to bring in only
what you need (love the idea for services and browsers but not for this
problem).
Al
On Mon, 2013-07-08 at 14:28 -0600, Matthew Moore wrote:
> Arch had a package called "libetc" that did exactly what you want, but
> its been unmaintained for years now. Someone forked it, though, and
> people on the Arch forums seem to have it working:
>
> https://github.com/sloonz/rewritefs
>
> I
On 2013-07-08, Kelly Clowers wrote:
> On Mon, Jul 8, 2013 at 7:55 AM, ha wrote:
> > Thanks Ralph, I guess it would do it.
> > But I didn't plan to separate the conf files completely, I was hoping for a
> > solution more alike Wilko's (if it works).
> > After all we all have .config file in our hom
On Mon, Jul 8, 2013 at 7:55 AM, ha wrote:
> Thanks Ralph, I guess it would do it.
> But I didn't plan to separate the conf files completely, I was hoping for a
> solution more alike Wilko's (if it works).
> After all we all have .config file in our home directory.
> It makes sense that all applica
Thanks Ralph, I guess it would do it.
But I didn't plan to separate the conf files completely, I was hoping
for a solution more alike Wilko's (if it works).
After all we all have .config file in our home directory.
It makes sense that all applications write their conf files there,
instead "rand
On Mon, 2013-07-08 at 15:04 +0200, Ralf Mardorf wrote:
> On Mon, 2013-07-08 at 14:44 +0200, ha wrote:
> > Would you care to explain how to accomplish that setup?
> > It would be nice to have only one file that contains configuration (like
> > etc/, let's say .conf/) and not to have to search troug
On Mon, 2013-07-08 at 14:44 +0200, ha wrote:
> Would you care to explain how to accomplish that setup?
> It would be nice to have only one file that contains configuration (like
> etc/, let's say .conf/) and not to have to search trough two dozens of
> dot files every time I click on the "Browse"
Would you care to explain how to accomplish that setup?
It would be nice to have only one file that contains configuration (like
etc/, let's say .conf/) and not to have to search trough two dozens of
dot files every time I click on the "Browse" button in whatever
application - just to find docu
On Mon, 8 Jul 2013 12:42:55 +0200
Wilko Fokken wrote:
Hello Wilko,
>As a (private) text prone Debian user, I like having my dot files
>out of the way and not stumbling between my working files.
What dot files? Ones you've created, or those that are generated by
apps you use?
If the latter, mo
On Mon, 2013-07-08 at 12:57 +0100, Tony van der Hoff wrote:
> So, leave them in $HOME, and create directories such as $HOME/work;
> $HOME/documents
Or even keep the hidden files in $HOME but instead of adding $HOME/work,
HOME/documents, add /home/work, /home/documents or /mnt/work etc..
FWIW I've
On 08/07/13 11:42, Wilko Fokken wrote:
> Moin mitnanner,
>
> As a (private) text prone Debian user, I like having my dot files
> out of the way and not stumbling between my working files.
>
> On the other hand, I dislike hiding them by file managers,
> because I want to discover them early at pos
On Mon, Jul 08, 2013 at 12:42:55PM +0200, Wilko Fokken wrote:
> Moin mitnanner,
>
> As a (private) text prone Debian user, I like having my dot files
> out of the way and not stumbling between my working files.
>
> On the other hand, I dislike hiding them by file managers,
> because I want to dis
17 matches
Mail list logo
