emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: bug: org-mouse broken
Date: Tue, 20 Sep 2011 10:39:27 -0700	[thread overview]
Message-ID: <CAJcAo8upmUAopMrVkxv1ckgabdUJp9oNTtvUqeH8WizNAs8Qsw@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8syAKi7O82iGFySK5K27itOOz6kioxanQXQBWaq4rHVRw@mail.gmail.com>

Org-mouse still broken.  I wonder if it would be safe to revert this
patch, or perhaps it's a bug in org-mouse.

On 2011-08-18, Samuel Wales <samologist@gmail.com> wrote:
> git bisect:
>
> 628ebf04f74afa8694945386c507bde06c3aac9e is the first bad commit
> commit 628ebf04f74afa8694945386c507bde06c3aac9e
> Author: Nicolas Goaziou <n.goaziou@gmail.com>
> Date:   Mon Jul 25 17:50:28 2011 +0200
>
>     Enforce white space after todo keywords
>
>     * lisp/org.el (org-set-regexps-and-options): enforce white space after
>       todo keyword, as word boundary isn't sufficient (i.e. in matches
> * TODO/this)
>
> :040000 040000 9786e7018273d86a894aecabac265e46429c233c
> ef1ffd65a9c8efa918dedfe5c157f0f1ef835923 M	lisp

  parent reply	other threads:[~2011-09-20 17:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19  5:56 bug: org-mouse broken Samuel Wales
2011-08-19  6:06 ` Samuel Wales
2011-09-20 17:39 ` Samuel Wales [this message]
2011-09-20 17:42   ` Samuel Wales
2011-09-22 14:19     ` Nicolas Goaziou
2011-09-22 16:26       ` Michael Brand
2011-09-22 18:25         ` Nicolas Goaziou
2011-09-22 18:45           ` Michael Brand
2011-09-23 10:54           ` Michael Brand
2011-09-23 16:45             ` Nicolas Goaziou
2011-09-23 17:00               ` Michael Brand
2011-09-25 10:19               ` Michael Brand
2011-09-28 15:53                 ` Nicolas Goaziou
2011-09-28 16:06                   ` Michael Brand
2011-11-03 18:03                   ` Michael Brand
2011-11-03 20:43                     ` Nicolas Goaziou
2011-11-03 21:10                       ` Michael Brand

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=CAJcAo8upmUAopMrVkxv1ckgabdUJp9oNTtvUqeH8WizNAs8Qsw@mail.gmail.com \
    --to=samologist@gmail.com \
    --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).