[Orgmode] How to turn off highlighting of headers matching tag search (Newbie)
Hi, I've done a search on tags appearing in my orgmode document. The relevant headers then appear highlighted in yellow in my document. How can I turn this highlighting off? Many thanks. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] How to turn off highlighting of headers matching tag search (Newbie)
On 13.03.2010 13:41, bar tomas wrote: Hi, I've done a search on tags appearing in my orgmode document. The relevant headers then appear highlighted in yellow in my document. How can I turn this highlighting off? Many thanks. Hi Thomas, that's yet another job for C-c C-c. - Jan ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Additional Export options
I have a few questions (or possible requests) regarding the export/publish capability. 1) Is there a way to get the buffer name or file name to be output as a keyword? I would like to know the source file used to publish the content. This would result in the filename being part of the post-amble along with author nfo and creation date. For example: #+OPTION: filename:t 2) Is there a way to set a pattern for export file name? For example, if my org file is called project-notes.org, when publishing notes on a given date, I would like to have the flexiblity to name the output file using a pattern such as filename--MM-DD-author-NTS.ext, where -MM-DD is the export date. This could be specified in an option. For example: #+EXPORT_OPTION: output: filename-export-date-author-NTS.ext PS. I have seen a thread where this was briefly discussed using options as drawer properties - :EXPORT_DATE:. In this scenario the export date was hard coded. I want to have the flexibility to use the actual publish instead of hard coding it. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] new spreadsheet features: field coordinates, multi line TBLFM with comments
Hi Carsten, hi all
1) field coordinates:
As a proposal I implemented the following to cover one of my spreadsheet use
cases: Why not let `...@#' and `$#' in Calc formulas (works also for Lisp
formulas) be substituted to the row or column number of the formula result
field?. The traditional Lisp formula equivalents are org-table-current-dline
and org-table-current-column. I believe it does not break the TBLFM syntax
for any other use.
My use case is an overview with the average annual relative changes of a time
series. Here is an example with averages for a history of 1 year up to 4 years:
| year | quote | 1 a | 2 a | 3 a | 4 a |
|--+---+---+---+---+---|
| 2005 |10 | | | | |
| 2006 |12 | 0.200 | | | |
| 2007 |14 | 0.167 | 0.183 | | |
| 2008 |16 | 0.143 | 0.155 | 0.170 | |
| 2009 |18 | 0.125 | 0.134 | 0.145 | 0.158 |
#+TBLFM: $3 = if(@# + 1 $#, ($2 / subscr(@-i$...@+i$2, @# + 1 - $#)) ^ (1 /
($# - 2)) - 1, string()); f3 :: $4 = if(@# + 1 $#, ($2 /
subscr(@-i$...@+i$2, @# + 1 - $#)) ^ (1 / ($# - 2)) - 1, string()); f3 ::
$5 = if(@# + 1 $#, ($2 / subscr(@-i$...@+i$2, @# + 1 - $#)) ^ (1 / ($# -
2)) - 1, string()); f3 :: $6 = if(@# + 1 $#, ($2 / subscr(@-i$...@+i$2,
@# + 1 - $#)) ^ (1 / ($# - 2)) - 1, string()); f3
The patch (the files with `---' were taken from org-version 6.34c):
==
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -2098,6 +2098,21 @@ table in that entry. REF is an absolute
described above for example @code{@@3$3} or @code{$somename}, valid in the
referenced table.
+...@subsubheading Field coordinates
+...@cindex field coordinates
+...@cindex coordinates, of field
+...@cindex row, of field coordinates
+...@cindex column, of field coordinates
+
+For Calc formulas and Lisp formulas @code{@@#} and @code{$#} can be used to
+get the row or column number of the field where the formula result goes.
+The traditional Lisp formula equivalents are @code{org-table-current-dline}
+and @code{org-table-current-column}. Example:
+
+...@example
+if(@@# % 2, $#, string()) @r{column number on odd lines only}
+...@end example
+
@node Formula syntax for Calc, Formula syntax for Lisp, References, The
spreadsheet
@subsection Formula syntax for Calc
@cindex formula syntax, Calc
--- a/lisp/org-table.el
+++ b/lisp/org-table.el
@@ -2243,6 +2243,21 @@ not overwrite the stored one.
(setq form (copy-sequence formula)
lispp (and ( (length form) 2)(equal (substring form 0 2) '()))
(if (and lispp literal) (setq lispp 'literal))
+
+ ;; Insert row number of formula result field
+ (while (string-match \...@# form)
+ (setq form
+ (replace-match
+(save-match-data
+ (format %d (org-table-current-dline)))
+t t form)))
+ ;; Insert column number of formula result field
+ (while (string-match \\$# form)
+ (setq form
+ (replace-match
+(save-match-data
+ (format %d (org-table-current-column)))
+t t form)))
;; Check for old vertical references
(setq form (org-table-rewrite-old-row-references form))
;; Insert remote references
==
2) self-edited multi line TBLFM with comments:
For me it would be great to have the now missing option to hack all the
formulas myself just directly, but rather into a multi line TBLFM with
comments than into the one line #+TBLFM:. For the use case above this would
look like:
[...]
| 2009 |18 | 0.125 | 0.134 | 0.145 | 0.158 |
#+BEGIN_TBLFM
$3 = if(@# + 1 $#, ($2 / subscr(@-i$...@+i$2, @# + 1 - $#)) ^
(1 / ($# - 2)) - 1, string()); f3 :: # rel. change for 1 year
$4 = if(@# + 1 $#, ($2 / subscr(@-i$...@+i$2, @# + 1 - $#)) ^
(1 / ($# - 2)) - 1, string()); f3 :: # average for 2 years
$5 = if(@# + 1 $#, ($2 / subscr(@-i$...@+i$2, @# + 1 - $#)) ^
(1 / ($# - 2)) - 1, string()); f3 :: # average for 3 years
$6 = if(@# + 1 $#, ($2 / subscr(@-i$...@+i$2, @# + 1 - $#)) ^
(1 / ($# - 2)) - 1, string()); f3# average for 4 years
#+END_TBLFM
I suggest to leave the one line #+TBLFM without the comment possibility to
avoid issues with the very nice write back to #+TBLFM when editing with e. g.
`C-c =' or moving rows and columns. In favor of a complexity reduction and to
avoid confusion I suggest to leave the #+BEGIN_TBLFM option without write
back and to unconditionally reject a trial to do it. Similar to the nice
reject when trying to edit column 1 with `C-c =' in the following example,
where #+TBLFM has been upset by self-editing it:
| 0 |
#+TBLFM: $1 = 0 :: $1 = 0
This way the implementation for the multi line TBLFM with comments could on
evaluation simply strip the comments from all
[Orgmode] many an agenda keyword search improvement
Here are agenda suggestions for org keyword searches that I
have been collecting.
All of them would be very useful (to me).
Is it better to use separate emails?
1. Colorize headlines as in the outline.
When I search for forums in org using M-x
org-agenda-dispatch s, I get an agenda that does not
colorize the italic part of the headline below.
* NAKA [#A] /email and forum/ forums :now:refile:
If it could be colorized normally, I would be able to find
the headline much faster.
2. Colorize matches.
Some hits are from headlines (i.e. forums is in the
headline), but others are from body text. These are not
distinguished. Also, regexp searches do not show what
matched, and you can't tell where the match is in a headline
easily.
These problems are solved by colorizing matches (e.g. using
the same face that isearch does).
3. Pre-seed isearch and isearch-regexp.
If you RET on a headline, you sometimes want to search for
the search expression (e.g. forums) in the body text.
(Optionally) pre-seeding isearch and isearch-regexp with the
search expression would allow you to not have to type it.
This would turn the entire expression, such as alpha beta
{gamma\|linoleic}, into a regular expression.
4. E-like mode for body matches.
If matches are in body text, perhaps the matching lines can
be shown under the headilnes with the matches highlighted.
5. Link type for agenda search.
Sometimes you want a todo item to do an agenda keyword search.
6. Colorize matches in other window.
When you show the outline buffer in the other window,
colorize matches there.
7. Search within results.
The / command is useful for searching for tags within
results (including body text) without having to incur the
overhead of an entire agenda search again.
I'd like the same thing for keyword searches. Searches are
very slow on my system, so I never refine searches. But I
would if I had this capability.
8. Or search within results and do other stuff.
I also have a proposal for an idea that supersedes #7 and
also allows more functionality. I alluded to it in previous
email in a footnote.
Suppose we could have a next command operates on the
selected entries (or ALL displayed entries if none
selected) command?
This could fold the / command and the command I am
requesting into a single facility that can then be used for
other purposes also. To do a todo search within a keyword
search, you just do the keyword search, run the command,
then do a todo search. Or any other command.
It could be on /. Current / behavior could be done with two
/es (first says next command is within results and second
says do tag search).
9. Search in attachments.
I have already covered this in another email. Perhaps the
discussion could be revived if there is enough interest.
Thanks.
Samuel
--
Q: How many CDC scientists does it take to change a lightbulb?
A: You only think it's dark. [CDC has denied a deadly disease for 25 years]
==
Retrovirus: http://www.wpinstitute.org/xmrv/index.html
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: many an agenda keyword search improvement
On 2010-03-13, Samuel Wales samolog...@gmail.com wrote: 7. Search within results. The / command is useful for searching for tags within results (including body text) without having to incur the overhead of an entire agenda search again. Correction: remove the including body text part to reduce confusion. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] :scale option in org-format-latex-options
When creating png images of latex fragments in org-create-formula-image, the :scale option in org-format-latex-options is not currently honoured (it's commented out). My dvipng documentation says -x num Set the x magnification ratio to num/1000. Overrides the magnification specified in the DVI file. Must be between 10 and 10. It is recommended that you use standard magstep values (1095, 1200, 1440, 1728, 2074, 2488, 2986, and so on) to help reduce the total number of PK files generated. num may be a real number, not an integer, for increased precision. I don't know what a magstep is, let alone a PK file, but it seems to suggest something like the patch below. Is there any reason not to make a change like this? --8---cut here---start-8--- diff --git a/lisp/org.el b/lisp/org.el index aa22309..e5d046e 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -15043,6 +15043,7 @@ Some of the options can be changed using the variable (font-height (get-face-font 'default)) (face-attribute 'default :height nil))) (scale (or (plist-get options (if buffer :scale :html-scale)) 1.0)) +(dvipng-scale (number-to-string (* 1000 scale))) (dpi (number-to-string (* scale (floor (* 0.9 (if buffer fnh 140.)) (fg (or (plist-get options (if buffer :foreground :html-foreground)) Black)) @@ -15078,7 +15079,7 @@ Some of the options can be changed using the variable (call-process dvipng nil nil nil -fg fg -bg bg -D dpi - ;;-x scale -y scale + -x dvipng-scale -y dvipng-scale -T tight -o pngfile dvifile) --8---cut here---end---8--- Also, this looks to me like a typo in the docstring of org-format-latex-options, is that right? --8---cut here---start-8--- diff --git a/lisp/org.el b/lisp/org.el index aa22309..e5d046e 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -2860,7 +2860,7 @@ This is a property list with the following properties: \$\ find math expressions surrounded by $...$ \$$\ find math expressions surrounded by $$$$ \\\(\ find math expressions surrounded by \\(...\\) - \\\ [\find math expressions surrounded by \\ [...\\] + \\\[\find math expressions surrounded by \\[...\\] :group 'org-latex :type 'plist) --8---cut here---end---8--- Dan ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] :scale option in org-format-latex-options
Hi Dan, Dan Davison wrote: When creating png images of latex fragments in org-create-formula-image, the :scale option in org-format-latex-options is not currently honoured (it's commented out). My dvipng documentation says -x num Set the x magnification ratio to num/1000. Overrides the magnification specified in the DVI file. Must be between 10 and 10. It is recommended that you use standard magstep values (1095, 1200, 1440, 1728, 2074, 2488, 2986, and so on) to help reduce the total number of PK files generated. num may be a real number, not an integer, for increased precision. I don't know what a magstep is, let alone a PK file, but it seems to suggest something like the patch below. Is there any reason not to make a change like this? I see two problems: First we should find out what x magnification and magstep actually is and why the manual suggests using these strange standard numbers. And second: At least dvipng shipped with debian testing , | This is dvipng 1.12 Copyright 2002-2008 Jan-Ake Larsson | dvipng 1.12 | kpathsea version 5.0.0 | Compiled with Freetype 2.3.11 | Using libft 2.3.11 | Using t1lib 5.1.2 ` does not have a -y option. Regards -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgpoIeFb2z7nR.pgp Description: PGP signature ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
