From: henry atting <nspm_01@literaturlatenight.de>
To: henry atting <nspm_01@literaturlatenight.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: align tags
Date: Sat, 04 Oct 2008 06:20:40 +0200 [thread overview]
Message-ID: <87od217zzb.fsf@literaturlatenight.de> (raw)
In-Reply-To: <87iqs9obpd.fsf@literaturlatenight.de> (henry atting's message of "Fri, 03 Oct 2008 19:00:46 +0200")
Zitat - henry atting * Fr Okt 03 2008 um 19:00 -
> Zitat - Nick Dokos * Fr Okt 03 2008 um 18:00 -
>
>> henry atting <nspm_01@literaturlatenight.de> wrote:
>>
>>> Zitat - John Rakestraw * Fr Okt 03 2008 um 12:58 -
>>>
>>> > On Fri, 03 Oct 2008 10:22:48 +0200
>>> > henry atting <nspm_01@literaturlatenight.de> wrote:
>>> >
>>> >> Is there a function which aligns tags in an org document?
>>> >
>>> > Does C-u C-c C-c do what you want?
>>>
>>> As far as I see it does what I want, but it an inconsistent way. I don't
>>> understand it.
>>> Expample:
>>>
>>> ** <2008-10-18 Sa>This is what I do at that date :holiday:
>>> ** TODO And here what I have to do on an other :schreiben:
>>>
>>> The variable org-tags-column is set to -90. And when I set the cursor
>>> behind any tag I get as resulting column 90.
>>>
>>
>> Maybe I'm missing the point but I don't see an inconsistency here.
>>
>> Are the two tags aligned flush right in your org file? They are not in the mail
>> message, but I suspect that's a tab handling problem in the almost infinite chain
>> from your org file to my inbox, and not an org-mode problem.
>
> No, they aren't aligned flush right, the above example looks exactly
> like the according part of an org file - I did not copy/paste it.
>
>> If they *are* flush right, then I think everything is as it should be, no? The
>> documentation for the variable you mention says:
>>
>> The column to which tags should be indented in a headline.
>> If this number is positive, it specifies the column. If it is negative,
>> it means that the tags should be flushright to that column. For example,
>> -80 works well for a normal 80 character screen.
>>
>> That's exactly what I get: when I set it to -90, they are flush right ending
>> at column 90; when I set it to 90, they are flush left starting at column 90.
>
> Same here, the tags end or start at column 90, but it *looks*
> inconsistent. If I put the cursor behind `:holiday:' the column number
> is 90, and if I put it behind `:schreiben:' it's 90, too.
> If you look at the above example you wouldn't expect this.
Aah, and the culprit is:
#+STARTUP: customtime
I was experimenting with in-buffer settings, this one caused the tag
display inconsistency. Now, that I have removed it, everything works as
it should.
Thanks to all
henry
prev parent reply other threads:[~2008-10-04 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 8:22 align tags henry atting
2008-10-03 10:58 ` John Rakestraw
2008-10-03 15:08 ` henry atting
2008-10-03 16:00 ` Nick Dokos
2008-10-03 17:00 ` henry atting
2008-10-04 4:20 ` henry atting [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87od217zzb.fsf@literaturlatenight.de \
--to=nspm_01@literaturlatenight.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).