Follow-up Comment #5, sr #111305 (group administration):

[comment #3 comment #3:]
> I don't object to adding the ability to edit a comment's content
> after posting.
> 
> However, I think the proper fix to the complaint that precipitated
> the request (the overlong URL) is the one I suggest in the newly
> opened sr #111307.  It shouldn't fall to the user to make sure a URL
> in a comment displays reasonably.  An algorithmic task like this is
> what automation is for.
I don't disagree with this.  However, the issue of excessively long lines,
with no obvious discretionary line break points, is far from the only issue
for which a ticket editing capability would be beneficial; (indeed, the
work⁠-⁠around implemented in response to sr #111307 offers a vast
improvement for long URLs, although it may not help in any case of other very
long entities with no specified line break opportunities).

That said, my own [https://savannah.gnu.org/bugs/index.php?60927#comment13
comment #13], on that same https://savannah.gnu.org/bugs/?60927 ticket
mentioned in [comment #0 my original submission], illustrates a further issue,
which a ticket editing capability could mitigate: that particular comment
includes a less than obvious typo, (U+2009 where I intended U+200B).  I'd love
to be able to fix that, but without a ticket editing capability, I cannot do
so.

Perhaps less relevant on savannah, but FWIW, the most common reason for using
this capability SourceForge, and on OSDN.net, was to correct the markup of
code samples, posted by user who didn't bother to acquaint themselves with the
appropriate markup conventions; I would encounter this in original ticket
submissions, just as often as in follow up comments; the usual effect was that
the code samples became unreadable, because elements of the code, which the
users were trying to illustrate, would be interpreted as markup.  Fortunately,
correction was possible, because an editing capability was available to the
original posters of malformed content, and to authorised project members.


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/support/?111305>

_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to