Submitted by Stephen Crawley on Fri, 08/15/2008 - 15:12.
The file name looks strange, but I think that this is not a FS bug. Instead I think it is an artifact of the way that the file's name is being generated. The .systemPrefs/plugin directory is providing persistence for preferences and I think the name is based on a plugin identifier.
Could someone who understands the plugin infrastructure please confirm this?
I think so too, but I'm not 100% sure either. Afair storing the systemPrefs on the filesystem is a temporarly workaround and will be replaced at some point, but levente should know more.
Anyway, why I'm replying is regarding the tab-completion which does not work for the given directory. Imho the tabcompletion should escape all special chars itself. With proper escaping (all '#',''','"' and '(') I can change to that directory (BTW, the directory/property will be created by some code in startawt if you want to test it).
Submitted by Stephen Crawley on Fri, 08/22/2008 - 13:21.
I have created a separate issue to address the tab completion bug. I'm marking this issue as "by design", since I think we are agreed this it is not a file system bug.
The stange directory name was created by the preferences framework. It detected that the plugin id for which a node was created contains the '.' character and encoded the id in base64. To prevent this I replaced '.' with '-' in the plugin id before passing it to the preferences api.
Fix committed.
#1
The file name looks strange, but I think that this is not a FS bug. Instead I think it is an artifact of the way that the file's name is being generated. The .systemPrefs/plugin directory is providing persistence for preferences and I think the name is based on a plugin identifier.
Could someone who understands the plugin infrastructure please confirm this?
#2
I think so too, but I'm not 100% sure either. Afair storing the systemPrefs on the filesystem is a temporarly workaround and will be replaced at some point, but levente should know more.
Anyway, why I'm replying is regarding the tab-completion which does not work for the given directory. Imho the tabcompletion should escape all special chars itself. With proper escaping (all '#',''','"' and '(') I can change to that directory (BTW, the directory/property will be created by some code in startawt if you want to test it).
#3
I have created a separate issue to address the tab completion bug. I'm marking this issue as "by design", since I think we are agreed this it is not a file system bug.
#4
#5
I think such an ugly bug can never be by design. It should be fixed wherever it is!
#6
The stange directory name was created by the preferences framework. It detected that the plugin id for which a node was created contains the '.' character and encoded the id in base64. To prevent this I replaced '.' with '-' in the plugin id before passing it to the preferences api.
Fix committed.
#7