[aur-dev] [PATCH] Wrap comments in <pre> tags, fixes FS#14391 - Aur-dev - lists.archlinux.org

newer
[aur-dev] Doubt in a TODO

[aur-dev] [PATCH] Wrap comments in <pre> tags, fixes FS#14391

older
[aur-dev] [PATCH] Convert the...

Manuel Tortosa

29 Jun 2011 29 Jun '11

8:32 p.m.

Exactly this, wrap the comments in <pre> tags allowing patches or at least better build output formatting. Greez

Attachments:

0003-Wrap-comments-in-pre-tags-fixes-FS-14391.patch (text/x-patch — 2.0 KB)

Show replies by date

Lukas Fleischer

29 Jun 29 Jun

9:22 p.m.

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?

Dan McGee

9:23 p.m.

On Wednesday, June 29, 2011, Manuel Tortosa 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.

Loui Chang

30 Jun 30 Jun

4:19 a.m.

On Wed 29 Jun 2011 16:23 -0500, Dan McGee wrote:

On Wednesday, June 29, 2011, Manuel Tortosa 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.

Lukas Fleischer

1 Jul 1 Jul

11:54 a.m.

On Wed, Jun 29, 2011 at 04:23:54PM -0500, Dan McGee wrote:

On Wednesday, June 29, 2011, Manuel Tortosa 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.

4691

Age (days ago)

4693

Last active (days ago)

Download

4 comments

4 participants

tags

participants (4)

Dan McGee
Loui Chang
Lukas Fleischer
Manuel Tortosa