emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Testing org-mode 4.37 (and a few suggestions)
Date: Mon, 12 Jun 2006 02:33:00 +0100	[thread overview]
Message-ID: <87ver788fn.fsf@tallis.ilo.ucl.ac.uk> (raw)

Heya,

some testing and suggestions...

* `org-version' is 4.36b in the last release (should be 4.37, no ?)

* I like the new `org-export' behavior, but (1) the [t] key ("insert
  the export option template") is not defined; (2) the [x] key (XOXO
  export) is somewhat confusing, since no global C-x key is available
  anymore (maybe use [O]?)

Suggestions:

* Keeping stored link after insertion often depends on the link we
  need to insert.  So `org-keep-stored-link-after-insertion' is OK,
  but some way to control this for every insertion (overriding the
  default value of the variable above) would be useful.

  Maybe C-u C-u C-u C-c C-l is okay ?

* What about a default description with stored links ?

  For example, the default for a file would be the name of the file,
  the default for a w3m buffer would be the title of the page, the
  default for a bibtex entry would be some apalike (or user defined)
  formatted string, and so on.

* org-narrow-to-current-level

  This is defined in org-blogging.el; i always use it when editing
  some big org file.


(defun org-narrow-to-current-level nil
  "Narrow to current level."
  (interactive)
  (narrow-to-region 
   (or (save-excursion
	 (re-search-backward "^\\(\\*+\\) " nil t))
       (point-min))
   (or (save-excursion
	 (re-search-forward
	  (concat "^"
		  (regexp-quote
		   (substring (match-string 1) 0
			      (1- (length (match-string 1)))))
			"\\*? ") nil t)
	 (match-beginning 0))
       (point-min))))


Best regards,

-- 
Bastien

next             reply	other threads:[~2006-06-12  1:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12  1:33 Bastien [this message]
2006-06-12  9:59 ` Testing org-mode 4.37 (and a few suggestions) Carsten Dominik
2006-06-12 13:26   ` Bastien
2006-06-12 20:57     ` Carsten Dominik
2006-06-12 21:18       ` Bastien

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=87ver788fn.fsf@tallis.ilo.ucl.ac.uk \
    --to=bzg@altern.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

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).