From: Richard Riley <rileyrgdev@googlemail.com>
To: Ben Alexander <bva@alexanderonline.org>
Cc: emacs-orgmode Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: Problem with org-toggle-timestamp-type
Date: Thu, 30 Oct 2008 16:46:51 +0100 [thread overview]
Message-ID: <wf8ws69jbo.fsf@development.richardriley.net> (raw)
In-Reply-To: <60C89E98-67D2-45E1-B996-57751B9A4C65@alexanderonline.org> (Ben Alexander's message of "Thu, 30 Oct 2008 17:21:57 +0200")
Ben Alexander <bva@alexanderonline.org> writes:
> I apologize if this is a repeat. It's in my sent items, but I haven't
> seen it on the list yet. I edited the message bit, and added a bit
> more:
>>
>> Hi!
>>
>> I cannot figure out how to use version control in general, and git
>> in particular. So I can't generate a proper patch. However, I think
>> there is a mistake with org-toggle-timestamp-type.
With regard to git:
I have been playing with git and its a bit of a muddle as there are so
many options and alternatives which cover similar command
subsets. Having just discovered dvc the waters are even muddier.
http://www.emacswiki.org/cgi-bin/wiki/Git
But if you use emacs 23 then most basic revision control commands are
there are described in the version control section of the emacs manual.
My personal favorite is here as it includes a good tutorial but, for
some reason, refuses to status my .emacs.d. But it works well with
org-mode project which you can clone. Note the use of the graphical tool
gitk too. It is also the only one which use ediff as a default and the
only one which provides graphical status bar indicators of your file's
git status.
http://tsgates.cafe24.com/git/git-emacs.html
The most promising one with regard to staging and branching is magit:
http://github.com/technomancy/magit/tree/master
And the author is generally online in the #emacs irc channel.
regards
richard.
>>
>> Currently, the message always returns "Timestamp is now active"
>> regardless of whether it is or not. I think this is because the
>> message is not inside the save-excursion block, so we can't be sure
>> whether point was outside the timestamp (just in front) or inside
>> (at the very end). Inside save-excursion, I think it is always
>> moved to the end, does the edit, and is moved outside.
>>
>> Also, I think the sense of the test is backwards. And for some
>> reason (if (equal (char-before) ?]) "in" "") didn't work (went to
>> elisp debugger). I can't read this much lisp, it's beyond me.
>>
>> So here's the change I made (to org-version 6.10c)
>>
>>
>> (defun org-toggle-timestamp-type ()
>> "Toggle the type (<active> or [inactive]) of a time stamp."
>> (interactive)
>> (when (org-at-timestamp-p t)
>> (save-excursion
>> (goto-char (match-beginning 0))
>> (insert (if (equal (char-after) ?<) "[" "<")) (delete-char 1)
>> (goto-char (1- (match-end 0)))
>> (insert (if (equal (char-after) ?>) "]" ">")) (delete-char 1)
>> (message "Timestamp is now %sactive"
>> (if (equal (char-before) ?>) "" "in")))))
>>
>> There's something else, and this might very well because my git repo
>> is not what emacs is actually running, and my modified Makefile
>> install target might be foobar.
>>
>> If I have a timestamp that looks like <2009-01-29 Thu>--<2009-01-29
>> Thu> and the cursor is in front of the first > symbol and then I hit
>> the S-<up> twice, my timestamp no longer is a range. It now looks
>> like [2009-01-30 Fri]
>>
> And if the cursor is in front of the the first < symbol and I hit the
> S-<up> key once (or if I use M-x org-toggle-timestamp-type), I get
> [2009-01-29 Thu]--<2009-01-29 Thu>
> but a second time, I get
> <2009-01-29 Thu]--<2009-01-29 Thu]
>
> That suggests to me that the regular expression isn't symmetric
> w.r.t. square brackets and curly brackets. I kinda know perl regex,
> but am completely unfamiliar with elisp's version.
>
>> I tried to look at the org-ts[r]?-regexp-* variables, but my eyes
>> crossed. Plus, I'm very afraid that any change I'd make would add
>> parentheses, and thereby screwup every (match-begin 8) in the code.
>>
>> TFOM*
>>
>> Ben
>>
>> ----
>> footnotes
>> * TFOM = Thanks for Org-Mode
>>
>>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
--
important and urgent problems of the technology of today are no longer the satisfactions of the primary needs or of archetypal wishes, but the reparation of the evils and damages by the technology of yesterday. ~Dennis Gabor, Innovations: Scientific, Technological and Social, 1970
next prev parent reply other threads:[~2008-10-30 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0A7CF9F9-391A-4424-AB1A-D124293AD9A8@alexanderonline.org>
2008-10-30 15:21 ` Problem with org-toggle-timestamp-type Ben Alexander
2008-10-30 15:46 ` Richard Riley [this message]
2008-11-01 13:48 ` Carsten Dominik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wf8ws69jbo.fsf@development.richardriley.net \
--to=rileyrgdev@googlemail.com \
--cc=bva@alexanderonline.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.