Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Michael Stapelberg <michael+sup@stapelberg.de>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Bugfix: Create dynamically growing fields (long filenames are now supported)
Date: Sat, 27 Feb 2010 03:18:17 -0500	[thread overview]
Message-ID: <1267258647-sup-2076@zyrg.net> (raw)
In-Reply-To: <1266271874-sup-6404@midna.zekjur.net>

Excerpts from Michael Stapelberg's message of 2010-02-15 17:13:00 -0500:
> Hi,
> 
> the attached patch modifies textfield.rb to create a dynamically growable field
> instead of one with a fixed size. The text field can now hold a dynamic amount
> of characters which is often necessary if you have long file names.
> 
> How to reproduce the bug:
> 1) mkdir -p /tmp/very/long-folder-name-foo-bar-baz/longer-than-one-line-foo-bar-bleh-bleh/maw-maw-maw-maw-maw-maw-maw-maw-maw-maw-maw
> 2) echo foo > /tmp/very/long-folder-name-foo-bar-baz/longer-than-one-line-foo-bar-bleh-bleh/maw-maw-maw-maw-maw-maw-maw-maw-maw-maw-maw/foo.txt
> 3) create a new message in sup and try to add the new file as an attachment
> 
> Please merge this one for the next release.
> 
> Best regards,
> Michael

Is this still necessary on latest master?
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2010-02-27  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 22:13 Michael Stapelberg
2010-02-27  8:18 ` Rich Lane [this message]
2010-02-27 12:45   ` Michael Stapelberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1267258647-sup-2076@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=michael+sup@stapelberg.de \
    --cc=sup-devel@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox