unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Olson <mwolson@gnu.org>
Subject: Re: [bug]org-mode with flyspell-mode freezes emacs
Date: Fri, 20 Oct 2006 18:05:23 -0400	[thread overview]
Message-ID: <871wp2wsm4.fsf@hariken.mwolson.org> (raw)
In-Reply-To: 85iriim5y9.fsf@lola.goethe.zz


[-- Attachment #1.1: Type: text/plain, Size: 971 bytes --]

David Kastrup <dak@gnu.org> writes:

> The question is why the information of the link has to be in the
> buffer text.

The purpose of this program is for the user to keep track of various
kinds of data in a way that can be viewed and exported conveniently,
similar (to some extent) to a wiki engine and personal organizer.

For links, which are colorized for the sake of visual appeal, the user
provides both the link and (optionally) the link description using the
markup syntax that Carsten described.  So of course it has to be in
the buffer text -- how else could changes be meaningfully saved?

-- 
Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/
Interests: Emacs Lisp, text markup, protocols -- Jabber: mwolson_at_hcoop.net
  /` |\ | | | Projects: Emacs, Muse, ERC, EMMS, Planner, ErBot, DVC
 |_] | \| |_| Reclaim your digital rights by eliminating DRM.
      See http://www.defectivebydesign.org/what_is_drm for details.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2006-10-20 22:05 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-15  4:20 [bug]org-mode with flyspell-mode freezes emacs Richard Stallman
2006-10-16  7:55 ` Carsten Dominik
2006-10-16  9:01 ` Carsten Dominik
2006-10-16 18:47   ` Richard Stallman
2006-10-17  4:33   ` Nick Roberts
2006-10-17 10:57     ` Carsten Dominik
2006-10-17 13:13       ` Carsten Dominik
2006-10-17 14:18         ` martin rudalics
2006-10-17 17:49         ` martin rudalics
2006-10-17 21:11           ` Carsten Dominik
2006-10-17 22:03             ` Stefan Monnier
2006-10-17 22:09               ` Lennart Borgman
2006-10-17 22:14                 ` David Kastrup
2006-10-17 22:26                   ` Lennart Borgman
2006-10-17 22:38                     ` David Kastrup
2006-10-17 22:44                       ` Drew Adams
2006-10-17 22:38               ` Carsten Dominik
2006-10-17 22:49                 ` David Kastrup
2006-10-18  4:26                   ` Carsten Dominik
2006-10-18  7:35                     ` David Kastrup
2006-10-20 22:05                       ` Michael Olson [this message]
2006-10-21  6:13                         ` David Kastrup
2006-10-21 18:30                           ` Michael Olson
2006-10-23  5:11                             ` Richard Stallman
2006-10-23 13:00                               ` Michael Olson
2006-10-22  0:24                           ` Stefan Monnier
2006-10-22 16:39                             ` David Kastrup
2006-10-18  0:28                 ` Stefan Monnier
2006-10-18  4:26                   ` Carsten Dominik
2006-10-18  4:14             ` Chong Yidong
2006-10-17 18:40       ` Richard Stallman
2006-10-17 20:45         ` martin rudalics
2006-10-18 10:41           ` Richard Stallman
     [not found] <m2lknmthc4.fsf@sl392.st-edmunds.cam.ac.uk>
2006-10-12 16:57 ` Leo

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871wp2wsm4.fsf@hariken.mwolson.org \
    --to=mwolson@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.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).