Tiny Core Base > Release Candidate Testing

tinycore_v3.4rc1

<< < (3/4) > >>

maro:
Whilst searching around for something else I noticed a couple of files where '/home/tc' is used as a hardcoded value representing the default users home directory:
* (1) in '/etc/init.d/services/tftpd' it probably needs the "usual" lookup from '/etc/sysconfig/tcuser',
* (2) in the .desktop file for 'fluff' (i.e. '/usr/share/applications/tinycore-filemgr.desktop') it probably means to replace Exec=fluff /home/tc with Exec=fluff ~ (which should "fix" the FLWM menu),
* (3) the 'fluff' executable also uses '/home/tc' when pressing 'Ctrl-H' no matter what is stated in '/etc/sysconfig/tcuser' (and one ends up with Loc1Path = /home/tc in '~/.fluff.conf'), and
* (4) the 'fluff_help.htm' (in '/usr/share/doc/tc') also makes a reference to '/home/tc', which might not be such a good idea.
Since the FLWM menu uses 'fluff DIR' it appears only "fair" that 'wbar' follows the same principle. That would probably mean a change in '/usr/share/wbar/dot.wbar' from c: exec fluff to c: exec fluff ~. Furthermore I wonder in which directory 'fluff' should start when called from a shell: currently it seems to be always '/' (i.e. the root), but maybe for many users the more "obvious" choice would be the current directory. As it happens it does not like fluff . whilst it behaves as expected with fluff ~

Still on the subject of 'fluff' one minor observation when starting it first time from a shell:

--- Code: ---Don't know how to process 'FileOwnerColWidth = 80
'...

--- End code ---
I guess this is probably harmless, but it might be better to avoid it.

roberts:
1, 2, and wbar addressed. I have passed on items 3, 4, starting with "." and code example to Mike. Fluff is still in active development. It is currently at 0.7.8. Good feedback. Thanks.

MikeLockmoore:
@maro:  Thanks for the feedback.  In the current version, Fluff will use the following priority to determine which directory to initially display:

1) The path specified on the command line

2) (If no path on the command line) the path specified by "StartPath" in the .fluff.conf file, but note that this needs to be an explicit path, "~" won't work in the config file

3) (If there is no .fluff.conf file, or the file lacks a StartPath statement) the root directory "/"

Initially starting in the current working directory of a terminal shell session does make some sense.  But then the "StartPath" setting option won't make sense, and should probably be dropped.  And that means that if a user wanted the wbar to launch Fluff in a certain directory, he or she would need to configure the wbar stuff.  Perhaps "." will work as the "StartPath" (I'll need to test this later... if it works, that is a work-around for people who want Fluff to start showing the current working directory.)

There are two buttons on the tool bar, which are initially configured to "Home" and "TCE", which are also triggered by the keyboard shortcuts like Ctrl+H.  As long as the first button is configured to the label "Home", Fluff will obtain the path to home via the $HOME environment variable, so it should automatically be correct even in the user does not log in as TC (but I have not tested this directly yet).  Will $HOME conflict with /etc/sysconfig/tcuser?  If so, who should win? Once we sort things, out, I will update the help document.

If the second button bar shortcut button is configured to the label "TCE", Fluff will obtain the path to it by reading /opt/.tce_dir, so it should also automatically adjust if the TCE directory changes for some reason.

The FileOwnerColWidth is an obsolete setting.  I will make sure it is not being written out any longer from Fluff.  Robert will need to make sure the .fluff.conf file that ships in TC Base's .iso does not include this obsolete setting.  (@Robert: Sorry that I neglected to mention this before.)

roberts:
Referencing /etc/sysconfig/tcuser instead of env HOME is for those processes that may be initiated during boot, i.e., HOME value not set. Fluff would not be such a boot time process. Therefore referencing env HOME should be all that is necessary. Which I believe it is. The "issue" is the default .fluff.conf which we can drop.

Let fluff create such upon initial use. The only reason that I provided /etc/skel.fluff.conf was at the time the .tcz file type and association were not defaulted. Since such is now the case. I don't see a reason for an initial .fluff.conf.

MikeLockmoore:
RobertS: understood and agreed.  Should I drop the "StartPath" setting and allow the wbar start script pass '~' as maro described?  Then Fluff would default to the current working directory unless there is a path passed into the command line. -- ML

Navigation

[0] Message Index

[#] Next page

[*] Previous page