[aur-dev] [PATCH] Wrap comments in <pre> tags, fixes FS#14391
Exactly this, wrap the comments in <pre> tags allowing patches or at least better build output formatting. Greez
On Wed, Jun 29, 2011 at 10:32:48PM +0200, Manuel Tortosa wrote:
Exactly this, wrap the comments in <pre> tags allowing patches or at least better build output formatting.
Greez
What's the motivation behind this one? Imho, comments are supposed to be comments - that is plain text messages without any special formatting. If we want bug tracking features, we should allow to upload patches (or attachments in general). Until then, pastebins should be sufficient. Opinions?
On Wednesday, June 29, 2011, Manuel Tortosa <manutortosa@gmail.com> wrote:
Exactly this, wrap the comments in <pre> tags allowing patches or at least better build output formatting.
-1, and I believe this isn't the first time this has been proposed. It makes everything else less readable at the expense of a few comments. Why not have a checkbox when entering a comment that allows you to mark it as code/fixed width? That way we don't screw of every existing package comment.
On Wed 29 Jun 2011 16:23 -0500, Dan McGee wrote:
On Wednesday, June 29, 2011, Manuel Tortosa <manutortosa@gmail.com> wrote:
Exactly this, wrap the comments in <pre> tags allowing patches or at least better build output formatting.
-1, and I believe this isn't the first time this has been proposed. It makes everything else less readable at the expense of a few comments.
Why not have a checkbox when entering a comment that allows you to mark it as code/fixed width? That way we don't screw of every existing package comment.
Brilliant Idea. Haha. Why didn't I think of that? I don't like patches and stuff in comments though.
On Wed, Jun 29, 2011 at 04:23:54PM -0500, Dan McGee wrote:
On Wednesday, June 29, 2011, Manuel Tortosa <manutortosa@gmail.com> wrote:
Exactly this, wrap the comments in <pre> tags allowing patches or at least better build output formatting.
-1, and I believe this isn't the first time this has been proposed. It makes everything else less readable at the expense of a few comments.
Why not have a checkbox when entering a comment that allows you to mark it as code/fixed width? That way we don't screw of every existing package comment.
Yeah, that sounds like a sane compromise. +1.
participants (4)
-
Dan McGee
-
Loui Chang
-
Lukas Fleischer
-
Manuel Tortosa