Fluff 0.9.5+ bugs and issues

[MikeLockmoore]

If you got 'em, post 'em here! Thanks.

NOTE: discussion of future issues is directed to this thread: http://forum.tinycorelinux.net/index.php?topic=9517.0.  Thanks.

[aus9]

hi

I am replying here instead of the wrong thread for bug v 0.9.0

1) sorry for any misleading on my last post....no results meant no results or hits for the .fluff.conf file
I do get hits for other fluffly stuff

2) so relooking at my hard drive and searching again its easier to see by just running

ls -al as a local user....file is called /home/tc/.fluff.conf

doing a search with root powers brings no extra results but is found with

sudo find / -name *fluff.conf

3)  Now running TC 3.6 in vbox here is similar commands and results



4) there is a suggestion that .fluff.conf is supposed to be also in /etc/skel but I can't spot it

[OldAdamUser2]

Clicking on "Help" in brings up the help menu with a line reading

BETA Version 0.8.x, January 2011

Should that be changed to 0.9.x?

Second thought: Can you add a search function to Fluff? I currently use MC for searches, but Fluff is so good in every other way . . .

[MikeLockmoore]

@aus9: Since Fluff will create a .fluff.conf file with default options if one is not found, I presume the Core Team decided it was not necessary to provide a default one in /etc/skel.

@OldAdamUser2: I will need to see why that help string is still like that... I provided an updated help file, but maybe that is not in the full 3.6 release?  Or maybe the older help file is being restored from your personal backup when TC boots?

Search is on this wish list for possible additions.

EDIT: Discussion on future features should be made in this thread: http://forum.tinycorelinux.net/index.php?topic=9517.0.  Thanks.

[roberts]

Help file is current.
Booting v3.6 base norestore displays
BETA Version 0.95, April 2011

No .fluff.conf needed in /etc/skel as the embedded default created by fluff is all that is needed to start.

Perhaps you have a fluff.tcz v0.8.x?

[OldAdamUser2]

Glad the help file lists the right version. I'm not using TC 3.6, but I downloaded the latest Fluff from Mike's code page. He probably updated one place and not the other.

[roberts]

I can see a potential problem with multiple sources and supporting external source from within this forum. Afterall this topic area is TCB Bugs. I am spending time verifying non Tiny Core base issues.

[MikeLockmoore]

@RobertS: Right.  I was just trying to verify it was an extension clouding the issue.

[aus9]

hi

Dear Gentlemen

as agreed I still can not find my fluff.conf but I booted up TC 3.6  in a virtual machine with nothing installed on virtual hard drives and used bootcode
tinycore norestore

2) After right hand clicking a file and adding an action in fluff....I can still not see any .fluff.conf file being created.

as per image



Please note that I ran

ls -al before and after tweaking my fluff manager

I repositioned the terminal for cosmetic reasons only

3) So consider this ....not a bug but maybe  a feature request with the following supporting waffle

a) I have a hard drive copy of .fluff.conf so am not concerned personally by not finding it in 3.6
b) But if others confirm that no conf file is created if they make changes,
maybe
it will impact on those using home persistence?

Thanks for reading

[Guy]

I have .fluff.conf

[MikeLockmoore]

@aus9:

Fluff works like this:

1) If ~/.fluff.conf file exists, Fluff opens it, reads the settings, then uses them to display the main window (window sizes, a set of file types and associations, some toolbar-related things, etc.)

2) If ~/.fluff.conf does not exist, these settings are set to default values, then Fluff uses those default values to present the main window (which includes an initial size that will fit in a 800x600 pixel display, a minimal set of file associations, etc.)

3) The user uses Fluff.  Fluff tracks your changes in window size, how width of the directory tree window, file associations, whether to show "hidden" dot files, etc.

4) When the user closes Fluff, the file ~/.fluff.conf is created, or re-created with the current settings.

5) Your .fluff.conf file would normally be persistent if you do the normal backup of /home/tc or have a persistent home in your boot settings.  So the next time Fluff starts, it will use the settings from the previous session. However, if home is not persistent, your Fluff settings would (of course) be lost and Fluff would re-create it again and again.

Therefore, if you go to look for the .fluff.conf file before you CLOSE Fluff the first time, you won't find it.  I don't consider this a bug... it is just a side effect of a design decision. 

If you want to see the default values, open fluff on a pristine base system then close it immediately.  The settings in the .fluff.conf file will be the default settings.  If you are trying to do something special regarding the .fluff.conf file or its settings, maybe PM and I will try to recommend a way to do what you want.

[tinypoodle]

Therefore, if you go to look for the .fluff.conf file before you CLOSE Fluff the first time, you won't find it.  I don't consider this a bug... it is just a side effect of a design decision. 

That's a behavior observed with a plethora of apps.   

[Guy]

When you paste something, it does not show up.

You need to either close fluff and reopen it to see it, or go to another directory and come back.

[Guy]

Try renaming a directory and see what happens.

I have been using it for 2 minutes, and have found 2 bugs, and one feature missing.

That is why, in the past, I have just given up using it.

These things should be obvious, if you just use it a little.

[Guy]

I tried to create a directory on a usb drive (using sudo). Got the message:

Cannot create directory. System returned (13): Permission denied.