Example -  winzip only supports 250 bytes in filenames:

http://kb.winzip.com/kb/entry/99/

Which suggests (because of the zip format) that fossil zip also has such a
limit, in which case display of such names in one particular view is the
least of the problems such names cause.

----- stephan
(Sent from a mobile device, possibly from bed. Please excuse brevity,
typos, and top-posting.)
On Mar 22, 2015 12:59 PM, "Stephan Beal" <[email protected]> wrote:

> Not unsolvable, of course, but imho not fossil's problem. Such names cause
> grief for many tools.
>
> ----- stephan
> (Sent from a mobile device, possibly from bed. Please excuse brevity,
> typos, and top-posting.)
> On Mar 22, 2015 2:07 AM, "jungle Boogie" <[email protected]> wrote:
>
>> On 21 March 2015 at 15:45, Stephan Beal <[email protected]> wrote:
>> > On Sat, Mar 21, 2015 at 10:58 PM, jungle Boogie <
>> [email protected]>
>> > wrote:
>> >>
>> >> I'm really hoping its a rare case where a file name is this long:
>> >>
>> >>
>> SWIGTYPE_p_f_p_switch_core_session_p_switch_event_p_switch_caller_profile_p_p_switch_core_session_p_p_apr_pool_t_enum_switch_originate_flag_t__switch_call_cause_t.cs
>> >
>> >
>> > Fossil is not the only tool which will have problems with such
>> > auto-generated names. i have seen generated Java class names so long
>> that
>> > they literally cannot be used on encrypted filesystems because the
>> encrypted
>> > names are larger than the unencrypted names, and too long for the
>> filesystem
>> > driver.
>> >
>>
>> Oh very interesting and thanks for the examples.
>>
>> Does this mean its an unsolvable problem? Sha1 hashes are truncated at
>> a user defined value so I was thinking file names could be truncated
>> (although I don't know what the value should be). The report list
>> allows you to click the file name so you'd be able to see the full
>> file. Then on that page, the extraordinary long file name won't wrap
>> and you'll have the same problem anyway.
>>
>> My above mentioned file has only two commits so its unfortunate that
>> such a nice report is ruined by a hardly changed file.
>>
>> > Some examples:
>> >
>> > https://bugs.launchpad.net/backintime/+bug/1359776
>> > https://bugs.launchpad.net/ecryptfs/+bug/344878
>> >
>> http://stackoverflow.com/questions/8239227/is-there-a-workaround-for-the-filename-length-limit-in-encfs
>> >
>> > --
>> > ----- stephan beal
>> > http://wanderinghorse.net/home/stephan/
>> > http://gplus.to/sgbeal
>> > "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
>> > those who insist on a perfect world, freedom will have to do." -- Bigby
>> Wolf
>> >
>> =
>>
>> Thanks!
>>
>> --
>> -------
>> inum: 883510009027723
>> sip: [email protected]
>> xmpp: [email protected]
>> _______________________________________________
>> fossil-users mailing list
>> [email protected]
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to