From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eddward DeVilla" Subject: Re: Re: list indentation Date: Sat, 9 Feb 2008 21:55:40 -0600 Message-ID: References: <41c818190802091345n5a49e5f2p23f50186144c33f3@mail.gmail.com> <41c818190802091450g6226c7abp86ad56eb09e8f2b1@mail.gmail.com> <41c818190802091709r68e36eeq1e42df06c6d8673c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JO3I7-0003vz-CO for emacs-orgmode@gnu.org; Sat, 09 Feb 2008 22:55:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JO3I5-0003v2-Lf for emacs-orgmode@gnu.org; Sat, 09 Feb 2008 22:55:42 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JO3I5-0003ul-AG for emacs-orgmode@gnu.org; Sat, 09 Feb 2008 22:55:41 -0500 Received: from wx-out-0506.google.com ([66.249.82.229]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JO3I4-0001hO-QO for emacs-orgmode@gnu.org; Sat, 09 Feb 2008 22:55:41 -0500 Received: by wx-out-0506.google.com with SMTP id s7so3912680wxc.24 for ; Sat, 09 Feb 2008 19:55:40 -0800 (PST) In-Reply-To: <41c818190802091709r68e36eeq1e42df06c6d8673c@mail.gmail.com> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: William Henney Cc: emacs-orgmode@gnu.org, cezar On Feb 9, 2008 7:09 PM, William Henney wrote: > But it causes problems to allow the same marker to be used at the > start and end. For instance, consider the following: > > ----- > - item one > - item two > ----- <- point is on this line > > When I hit TAB, how is org to know whether the "-----" is supposed to > start a new sublist (and so should be indented 3 spaces) or is meant > to end the preceding list (and so should not be indented)? True. I wasn't counting on tab to always get that right. I usually hit M-RET for a sibling entry and M-RET M-right for a sub list I was counting on the indent to determine if it was a sub-list. Otherwise, it doesn't matter if it's and end or beginning, at least in my mind. Once I set an indent, I'd like it to stay though. I have folding lists, so I probably don't appreciate some of the issues. When I hit tab on an existing item, it folds or unfolds. > That is why I proposed that IF we are to have both start and end > markers, THEN they need to be distinct. However, I now think that it > would be better to just have end markers. Personally, I would prefer > "-/" for the XMLish feel. My objections to "-----" are I'm afraid you won't win me over with xml. I'm not fond of it. > 1. It is hard to remember (was it 5 dashes or 4?) I'd say five or more and left org format it. But then again, I'm not really tied to it. The hline was my first guess at something. It puts it in a box. I kind of like that. I'll probably find a case where I wouldn't though. > 2. It is a pain to type when you have the "tex" input method turned on I can't argue that. I've never used the tex input method. > 3. It conflicts with existing usage (sec 12.6.5 of the manual) > > * A line consisting of only dashes, and at least 5 of them, will be > exported as a horizontal line (`
' in HTML). Actually, I was thinking of having an indented hline to box in the list, but again that may be plain wrong. Also, I thought the hline had to start at the beginning of the line. My mistake. In any case, I'm just trying to come up with something that does the job but is not an eye sore in the org buffer. I'm looking for something that visually looks like a natural footer or terminator in plain text. (And a footer ought to be able to be preceeded by a header.) I know the significance of the '/' in xml, but visually, it doesn't look right to my eyes. Aside from the meaning in xml code, it does say end-of-list to me. If anything, it seems to connect the preceeding and proceeding text, like this/that. The dashes draw a dividing line. Edd