Mailing List Archive: Trac: Tickets

[The Trac Project] #3277: "Break" button and treat <cr> as break

Index | Next | Previous | View Threaded

noreply at edgewall

Jun 16, 2006, 9:22 AM

Post #1 of 8 (1339 views)
Permalink

[The Trac Project] #3277: "Break" button and treat <cr> as break

#3277: "Break" button and treat <cr> as break
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: jonas
Type: enhancement | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
Please consider the following 2 thing:
* Adding a button that would insert {{{[[BR]]}}} when clicked
* Treating carriage return as a new line

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/3277>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
Trac-Tickets[at]lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac-tickets

noreply at edgewall

Jun 18, 2006, 4:58 PM

Post #2 of 8 (1306 views)
Permalink

Re: [The Trac Project] #3277: "Break" button and treat <cr> as break [In reply to]

#3277: "Break" button and treat <cr> as break
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: eblot
Type: enhancement | Status: assigned
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: toolbar |
-------------------------+--------------------------------------------------
Changes (by eblot):

* keywords: => toolbar
* owner: jonas => eblot
* status: new => assigned

Comment:

Please find a patch that adds a ''line break'' button to the existing wiki
toolbar.[[BR]]
You'll need to apply the patch file ''and'' overwrite the existing bitmap
file with the attached one)

The second proposition (to treat a line break in the wiki edit area as a
carriage return) would break existing wiki syntax, if not removing a very
useful editing feature.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/3277>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
Trac-Tickets[at]lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac-tickets

noreply at edgewall

Jun 19, 2006, 9:22 AM

Post #3 of 8 (1300 views)
Permalink

Re: [The Trac Project] #3277: "Break" button and treat <cr> as break [In reply to]

noreply at edgewall

Jun 19, 2006, 9:32 AM

Post #4 of 8 (1303 views)
Permalink

Re: [The Trac Project] #3277: "Break" button and treat <cr> as break [In reply to]

#3277: "Break" button and treat <cr> as break
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: eblot
Type: enhancement | Status: assigned
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: toolbar |
-------------------------+--------------------------------------------------
Comment (by eblot):

I'm not sure whether a button is required to save a double hit on the
''return'' key in this case.[[BR]]
I was thinking about a shortcut to save from typing the long `[[BR]]`
syntax.

Btw, the proposed button refers to a carriage return + line feed, whereas
a `\n\n` introduces a paragraph break.

In other words, the question is: should the button produce a line break
(`[[BR]]`) or a paragraph break (`\n\n`)?

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/3277>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
Trac-Tickets[at]lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac-tickets

noreply at edgewall

Jun 19, 2006, 11:05 AM

Post #5 of 8 (1293 views)
Permalink

Re: [The Trac Project] #3277: "Break" button and treat <cr> as break [In reply to]

#3277: "Break" button and treat <cr> as break
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: eblot
Type: enhancement | Status: assigned
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: toolbar |
-------------------------+--------------------------------------------------
Comment (by mgood):

Well, I don't think the buttons generally save time. I see them more as a
way for new users to use some syntax if they haven't read the
WikiFormatting docs yet. I think that the `[[BR]]` should be used
sparingly, but giving it a button would seem to encourage its use as a
common practice. It sounds like the reporter has encountered users
confused how to start a new line, but based on the usage of `[[BR]]` I've
seen on this site, most would've been more appropriate as a new paragraph.
If a `[[BR]]` button is deemed necessary I think that it should be
preceded by a `\n\n` button with the "¶" symbol.

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/3277>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
Trac-Tickets[at]lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac-tickets

noreply at edgewall

Jun 19, 2006, 12:00 PM

Post #6 of 8 (1307 views)
Permalink

Re: [The Trac Project] #3277: "Break" button and treat <cr> as break [In reply to]

noreply at edgewall

Jun 19, 2006, 3:54 PM

Post #7 of 8 (1299 views)
Permalink

Re: [The Trac Project] #3277: "Break" button and treat <cr> as break [In reply to]

noreply at edgewall

Jun 24, 2006, 7:02 AM

Post #8 of 8 (1294 views)
Permalink

Re: [The Trac Project] #3277: "Break" button and treat <cr> as break [In reply to]

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com