Re:Re: New user experience ct'd: exporting citations into LaTeX (9.5)

[tumashu]

#+print_bibliography seem to not document in info.
(require 'oc-csl) is not too.







--
发自我的网易邮箱手机智能版



- Original Message -
From: "Bruce D'Arcus" 
To: "Leszek Wroński" 
Cc: org-mode-email 
Sent: Wed, 13 Oct 2021 17:34:50 -0400
Subject: Re: New user experience ct'd: exporting citations into LaTeX (9.5)

Try adding this where you want the bibliography.


#+print_bibliography:






On Wed, Oct 13, 2021 at 5:27 PM Leszek Wroński  wrote:
>
> Guys,
>
> thank you very much for your responses to my previous query. (I will
> study the ebib package more closely; as of now it does not seem to
> work with the file fields in my Mendeley-created .bib file. (Yes, I
> promise will stop using Mendeley.))
>
> I wanted to try the two LaTeX export processors mentioned in the 15.2
> section of the manual: natbib and biblatex. My .org file has a
> #+bibliography line specifying my .bib (which is correct, since
> inserting citations is now working). I put both (use-package
> oc-natbib) and (use-package oc-biblatex) in my .emacs . (I've used
> natbib for years when writing .tex documents; I don't know biblatex.)
>
> The situation is as follows:
> -- if I put #+cite_export: natbib at the beginning of my .org file,
> then C-c C-e l L gives me a LaTeX file which does *not* specify the
> .bib file; it has \citep{} commands where they should be, but of
> course bibtex doesn't know what to do with them;
> -- if I use #+cite_export: biblatex instead, then the resulting .tex
> file does contain the \addbibresource{} line pointing to my .bib , and
> \autocite{} commands where citations should be; however, I simply
> cannot get this to work: Biber works alright, but eventually pdflatex
> gives me the following error:
>
> --
> ERROR: LaTeX3 Error: Mismatched LaTeX support files detected.
>
> --- TeX said ---
> (LaTeX3)Loading 'l3backend-pdftex.def' aborted!
> (LaTeX3)
> (LaTeX3)The L3 programming layer in the LaTeX format
> (LaTeX3)is dated 2021-01-09, but in your TeX tree the files require
> (LaTeX3)at least 2021-02-18.
> ---
>
> which I'm unable to get rid of. (This is of course not a question for
> this group but if anyone had similar problems I'd be grateful for
> pointers ;-);  fmtutil-sys --all and fmtutil-user --all did nothing to
> alleviate this)
>
> So: I'd really like to keep using natbib and make it somehow insert
> the information about the .bib file into the .tex when exporting. How
> do I do that?
>
> Thank you again for your help!
>
> Best regards,
>
> Leszek.
>

Re:[PATCH] The align of time is not beautiful as 9.4 when I update to org 9.5.

[tumashu]

At 2021-10-04 15:48:49, "Ihor Radchenko"  wrote:
>tumashu  writes:
>
>> Hello:
>>
>>
>> When I update to org 9.5,  I find that  the align of time like "7:00" has 
>> been changed.
>>
>> I think the new style is not beautiful as old style.
>>  
>> 1. New style look like not align to  the first char, for the width of 9 
>> looks like > 1
>> 2. the old style is align ":"
>
>The attached patch should fix the issue. Please, test it though. I do
>not use time grid regularly.

If change s1, I think s2 should be deal with too, by the way, what about change 
the below function?

```
(defun org-agenda-time-of-day-to-ampm-maybe (time)
  "Conditionally convert TIME to AM/PM format.
This is based on `org-agenda-timegrid-use-ampm'."
  (if org-agenda-timegrid-use-ampm
  (org-agenda-time-of-day-to-ampm time)
time))
^^^
```

Another way is creating a new function for the below code, so user can advice 
it to full control time string format.

```
(cond (s2 (concat
  (org-agenda-time-of-day-to-ampm-maybe s1)
  "-" (org-agenda-time-of-day-to-ampm-maybe s2)
  (when org-agenda-timegrid-use-ampm " ")))
 (s1 (concat
  (org-agenda-time-of-day-to-ampm-maybe s1)
  (if org-agenda-timegrid-use-ampm
  (concat time-grid-trailing-characters " ")
time-grid-trailing-characters)))
 (t ""))

```


>
>Best,
>Ihor
>

The align of time is not beautiful as 9.4 when I update to org 9.5.

[tumashu]

Hello:


When I update to org 9.5,  I find that  the align of time like "7:00" has been 
changed.

I think the new style is not beautiful as old style.
 
1. New style look like not align to  the first char, for the width of 9 looks 
like > 1
2. the old style is align ":"


Feng.

Re:Bug: ODT export of Chinese text inserts spaces for line breaks

[tumashu]

You can try the below config :-)





(defun eh-org-wash-text (text backend _info)
  "导出 org file 时，删除中文之间不必要的空格。"
  (when (or (org-export-derived-backend-p backend 'html)
(org-export-derived-backend-p backend 'odt))
(let ((regexp "[[:multibyte:]]")
  (string text))
  ;; org-mode 默认将一个换行符转换为空格，但中文不需要这个空格，删除。
  (setq string
(replace-regexp-in-string
 (format "\\(%s\\) *\n *\\(%s\\)" regexp regexp)
 "\\1\\2" string))
  ;; 删除粗体之后的空格
  (dolist (str '("" "" "" ""))
(setq string
  (replace-regexp-in-string
   (format "\\(%s\\)\\(%s\\)[ ]+\\(%s\\)" regexp str regexp)
   "\\1\\2\\3" string)))
  ;; 删除粗体之前的空格
  (dolist (str '("" "" "" "" ""))
(setq string
  (replace-regexp-in-string
   (format "\\(%s\\)[ ]+\\(%s\\)\\(%s\\)" regexp str regexp)
   "\\1\\2\\3" string)))
  string)))

(add-hook 'org-export-filter-headline-functions #'eh-org-wash-text)
(add-hook 'org-export-filter-paragraph-functions #'eh-org-wash-text)













在 2021-06-29 11:47:06，"James Harkins"  写道：
>Consider the following org document.
>
>* Test
>1本人不想亲自拿到学历学位证书、急于离校者,可书面委托他人代领学历学位证
>书,29日起即可离校;2本人想亲自领取学历学位证书者,按学校规定的程序及有关
>要求办理离校手续,领取相关证书后离校;
>
>This was produced by pasting in a single, long line, and then using alt-Q (a 
>normal thing to do, and good for readability, because org-mode doesn't wrap 
>lines by default).
>
>Exporting to ODT produces the following (body text, omitting titles, headers 
>and such).
>
>1本人不想亲自拿到学历学位证书、急于离校者,可书面委托他人代领学历学位证 书,29日起即可离校;2本人想亲自领取学历学位证书者,按学校规定的程序及有关 
>要求办理离校手续,领取相关证书后离校;
>
>Between 证 and 书, and between 关 and 要, there is a space. Chinese typography 
>does not allow for spaces mid-sentence.
>
>So, it would make sense to add a rule to the exporter: if one of the 
>characters before or after a source-text line break is a Chinese, Japanese or 
>Korean character, do not add a space. (The space is valid, of course, if the 
>characters on either side of the line breaks are Roman or [I would guess] 
>Cyrillic as well.)
>
>(Side note: Exporting to a LaTeX buffer shows that the line breaks have been 
>copied into the .tex document as is -- but, provided that you have a 
>`usepackage{xeCJK}` in the preamble, LaTeX produces correct, space-free 
>output. So -- Org "gets away with it" because of LaTeX's handling of CJK text. 
>It seems for ODT, Org needs to handle the spacing within its own logic.)
>
>This is org 9.1.9... bit old, I know, but I'm gonna take a wild guess that 
>this has not been a high-visibility issue.
>
>hjh

Re:Re:Re: [PATCH] Add 'simple option to org-fast-tag-selection-single-key.

[tumashu]

>I think (setq org-use-fast-tag-selection nil) do not work well with ivy, 
>selectrum or vertico.

>
>I like the below idea, but seem to no progress.
> https://lists.gnu.org/archive/html/emacs-orgmode/2020-07/msg00222.html

If this patch is hard to merge, I think my patch is a conside way, for it 
nearly doesn't affect other places 

 

Re:Re: [PATCH] Add 'simple option to org-fast-tag-selection-single-key.

[tumashu]

At 2021-05-01 23:20:24, "Bastien"  wrote:
>Hi tumashu,
>
>tumashu   writes:
>
>> This is v2 patch,   use completing-read-multipul.
>
>Thanks for the patch.  You can already do this:
>
>(setq org-use-fast-tag-selection nil)
>
>Then you'll be able to select tags the way you implemented it
>with this simple mode.

I think (setq org-use-fast-tag-selection nil) do not work well with ivy, 
selectrum or vertico.

I like the below idea, but seem to no progress.
 https://lists.gnu.org/archive/html/emacs-orgmode/2020-07/msg00222.html

>
>-- 
> Bastien

Re:[PATCH] Add 'simple option to org-fast-tag-selection-single-key.

[tumashu]

This is v2 patch,   use completing-read-multipul.

















At 2021-04-15 09:25:03, "tumashu"  wrote:

Hello


I have added  'simple option to org-fast-tag-selection-single-key,  please 
try and comment :-)


   (setq org-use-fast-tag-selection t)
   (setq org-fast-tag-selection-single-key 'simple)


   ;; better use vertico or selectrum :-)

   ;; (require 'vertico)
   ;; (vertico-mode 1)


thanks!


0001-Add-simple-option-to-org-fast-tag-selection-single-k.patch
Description: Binary data

[PATCH] Add 'simple option to org-fast-tag-selection-single-key.

[tumashu]

Hello


I have added  'simple option to org-fast-tag-selection-single-key,  please 
try and comment :-)


   (setq org-use-fast-tag-selection t)
   (setq org-fast-tag-selection-single-key 'simple)


   ;; better use vertico or selectrum :-)

   ;; (require 'vertico)
   ;; (vertico-mode 1)


thanks!


0001-Add-simple-option-to-org-fast-tag-selection-single-k.patch
Description: Binary data

About completion-ignore-case in org-tags-completion-function

[tumashu]

In org-tags-completion-function,  completion-ignore-case force nil, 
what about set it to t?

tags are case-sensitive,  wile this function is used to search tag.


(defun org-tags-completion-function (string _predicate  flag)
  "Complete tag STRING.
FLAG specifies the type of completion operation to perform.  This
function is passed as a collection function to `completing-read',
which see."
  (let ((completion-ignore-case nil);tags are case-sensitive
(confirm (lambda (x) (stringp (car x
(prefix ""))
(when (string-match "^\\(.*[-+:&,|]\\)\\([^-+:&,|]*\\)$" string)
  (setq prefix (match-string 1 string))
  (setq string (match-string 2 string)))
(pcase flag
  (`t (all-completions string org-last-tags-completion-table confirm))
  (`lambda (assoc string org-last-tags-completion-table)) ;exact match?
  (`nil
   (pcase (try-completion string org-last-tags-completion-table confirm)
 ((and completion (pred stringp))
  (concat prefix
  completion
  (if (and org-add-colon-after-tag-completion
   (assoc completion org-last-tags-completion-table))
  ":"
"")))
 (completion completion)))
  (_ nil

Re:Re: Agenda follow mode + indirect window settings

[tumashu]

At 2020-11-17 12:52:06, "Kyle Meyer"  wrote:
>Gerardo Moro writes:
>
>> Hi,
>>
>> I want my agenda to have follow-mode active when starting Emacs.
>> I suppose this would do the trick?
>>
>> (setq org-agenda-start-with-follow-mode t)
>> (setq org-agenda-follow-indirect t)
>>
>> 1) Do I need both? I have observed that having only the second one does not
>> work.
>
>The first one causes new agenda buffers to start with
>org-agenda-follow-mode enabled.  Even if it's not enabled initially, you
>can toggle it with F.
>
>The second is in effect when org-agenda-follow-mode is enabled.
>
>> 2) Is there a way to make the "indirect" window populate the vertically
>> existing window (I always work with the frame split in two vertically).
>> Right now it shows in a very small window beneath the agenda.
>
>I think with the way things are written at the moment you're best bet
>would be to try to rearrange afterwards (say with advice after
>org-agenda-tree-to-indirect-buffer).  Ideally the current behavior would
>be achieved in a way that would allow the user to control the result
>with things like display-buffer-overriding-action and
>display-buffer-alist, but I suspect that'd take a substantial rework.

I use the below config, maybe useful...


(define-key org-agenda-mode-map (kbd "SPC") 'eh-org-agenda-show-and-scroll-up)
(define-key org-agenda-mode-map (kbd "") 
'eh-org-agenda-show-and-scroll-up)

(defvar eh-org-agenda-show-window-point nil)
(defun eh-org-agenda-show-and-scroll-up ( arg)
  (interactive "P")
  (let ((win (selected-window)))
(if (and (window-live-p org-agenda-show-window)
 (eq this-command last-command))
(progn
  (select-window org-agenda-show-window)
  (if (eq eh-org-agenda-show-window-point (window-point))
  (progn
(goto-char (point-min))
(message "已经滚动到底，返回第一行！"))
(ignore-errors (scroll-up))
(setq eh-org-agenda-show-window-point (window-point
  (org-agenda-goto t)
  (org-show-entry)
  (let ((org-indirect-buffer-display 'current-window))
(org-tree-to-indirect-buffer)
;; 隐藏 indirect buffer
(rename-buffer (concat " " (buffer-name
  (if arg (org-cycle-hide-drawers 'children)
(org-with-wide-buffer
 (narrow-to-region (org-entry-beginning-position)
   (org-entry-end-position))
 (org-show-all '(drawers
  (setq org-agenda-show-window (selected-window)))
(select-window win)))

Re: [O] [PATCH] Add org-agenda-show-indirect variable

[tumashu]

At 2019-09-01 22:28:00, "Adam Porter"  wrote:
>tumashu  writes:
>
>> +  (when org-agenda-show-indirect
>> +(let ((org-indirect-buffer-display 'current-window))
>> +  (org-tree-to-indirect-buffer)
>> +  ;; hide indirect buffer in ibuffer
>> +  (rename-buffer (concat " " (buffer-name)
>
>1.  That does not affect only ibuffer, but most any code that lists
>buffers.
>
>2.  Please don't hide indirect buffers this way.  The user won't be able
>to switch back to it without enabling the display of hidden buffers.
>That will be unexpected, and many users wouldn't even know that such a
>thing can be done.  So if the user was working in that indirect buffer,
>how will he get back to it?

>Also, indirect buffers are not automatically cleaned up; according to
>the manual, if their base buffer is killed, they merely cannot be made
>active again, so hiding them is not a good idea.

In this condition,  indirect buffer is regard as a kind of *tmp* buffer, it 
should
be showed only when org-agenda-show-and-scroll-up is called, so hide 
indirect buffers should be a good idea.



>
>3.  What if such an indirect buffer already exists?  i.e. what if the
>user activates the command more than once?  It would be good to avoid
>creating multiple indirect buffers pointing to the same subtree.

Seem to no this problem, org-tree-to-indirect-buffer can deal with this .

>
>4.  You could give the indirect buffer a useful name, which would also
>make it possible to reuse indirect buffers if the user activates the
>command more than once.  For example, I use this code in my config:

Do not reuse indirect buffer. for it is a kind of "tmp" buffer.

>
>#+BEGIN_SRC elisp
>(defun ap/org-tree-to-indirect-buffer ( arg)
>  "Create indirect buffer and narrow it to current subtree.
>The buffer is named after the subtree heading, with the filename
>appended.  If a buffer by that name already exists, it is
>selected instead of creating a new buffer."
>  (interactive "P")
>  (let* ((new-buffer-p)
> (buffer-name
>  (let* ((level (org-outline-level))
> (heading-string (org-link-display-format
>  (org-get-heading t t
>(concat heading-string "::" (buffer-name
> (new-buffer
>  (or (get-buffer buffer-name)
>  (prog1 (condition-case nil
> (make-indirect-buffer (current-buffer)
>   buffer-name 'clone)
>   (error (make-indirect-buffer (current-buffer)
>buffer-name)))
>(setq new-buffer-p t)
>(switch-to-buffer new-buffer)
>(when new-buffer-p
>  (rename-buffer buffer-name)
>  (org-narrow-to-subtree
>
>(advice-add 'org-tree-to-indirect-buffer
>:override 'ap/org-tree-to-indirect-buffer)
>#+END_SRC
>

[O] [PATCH] Add org-agenda-show-indirect variable

[tumashu]

0001-Add-org-agenda-show-indirect-variable.patch
Description: Binary data

Re: [O] org-tags-match-list-sublevels is very useful in some condition, why we will semi-obsolete it?

[tumashu]

At 2019-03-22 04:55:25, "Nicolas Goaziou"  wrote:
>Hello,
>
>tumashu  writes:
>
>> (defcustom org-tags-match-list-sublevels t
>>   "...
>> This variable is semi-obsolete and probably should always be true.  It
>> is better to limit inheritance to certain tags using the variables
>> `org-use-tag-inheritance' and `org-tags-exclude-from-inheritance'."
>>
>> ...
>>
>>
>> "org-tags-match-list-sublevels  +  search +LEVEL>n " is a very useful tip, 
>> if you have many sublevels with many different tags,
>> it can not lost search results nearly, why we will semi-obsolete it?
>
>I do not understand your remark. Could you clarify what you mean? Do you
>have any use case for a nil `org-tags-match-list-sublevels' that cannot
>be handled with tag inheritance?
>
>Thank you.
>
>Regards,
>
>-- 
>Nicolas Goaziou

 I use a refs.org to manage my document, which is like the below example, but 
have many many headlines.

---
* story   :story:
** story1
** story2
*** sky :sky:
** story3
*** sky :sky:
** ...
** story100

* sky   :sky:
** sky1
*** sky story :story:
** sky2
** sky2
*** sky story :story:

--

(setq org-tags-match-list-sublevels nil) 

I seach "story" info with: "story+LEVEL>1", if I want to know more details, I 
search "story+LEVEL>2 ... 3 ... 4"  with  a user-define one key command help.


Sorry for my pool English :-(

[O] org-tags-match-list-sublevels is very useful in some condition, why we will semi-obsolete it?

[tumashu]

(defcustom org-tags-match-list-sublevels t
  "...
This variable is semi-obsolete and probably should always be true.  It
is better to limit inheritance to certain tags using the variables
`org-use-tag-inheritance' and `org-tags-exclude-from-inheritance'."

...


"org-tags-match-list-sublevels  +  search +LEVEL>n " is a very useful tip, if 
you have many sublevels with many different tags,
it can not lost search results nearly, why we will semi-obsolete it?

Re: [O] [PATCH] org-agenda: Add org-agenda-breadcrumbs-separator

[tumashu]

Added info to ORG-NEW


At 2019-03-21 21:49:14, "Nicolas Goaziou"  wrote:
>Hello,
>
>tumashu  writes:
>
>> From 7b94df17217c116c882e8a080f686b626c82f45e Mon Sep 17 00:00:00 2001
>> From: Feng Shu 
>> Date: Thu, 21 Mar 2019 12:49:42 +0800
>> Subject: [PATCH] org-agenda: Add org-agenda-breadcrumbs-separator
>>
>> * lisp/org-agenda.el (org-agenda-breadcrumbs-separator): New variable.
>> (org-agenda-format-item): Use org-agenda-breadcrumbs-separator
>
>LGTM! Thank you.
>
>Could you provide also provide an entry in ORG-NEWS (in Miscellaneous)
>and send it again?
>
>Regards,
>
>-- 
>Nicolas Goaziou


0001-org-agenda-Add-org-agenda-breadcrumbs-separator.patch
Description: Binary data

[O] [PATCH] org-agenda: Add org-agenda-breadcrumbs-separator

[tumashu]

0001-org-agenda-Add-org-agenda-breadcrumbs-separator.patch
Description: Binary data

Re: [O] [PATCH] Let radio target works well with Chinese

[tumashu]

在 2019-02-25 20:31:24，"Nicolas Goaziou"  写道：
>Hello,
>
>"Feng Shu"  writes:
>
>> * lisp/org.el (org-update-radio-target-regexp): Let radio target works well 
>> with Chinese
>
>Thank you.
>
>> There is no need to force split words with the help
>> of space for Chinese, this change let the below
>> example works well.
>>
>> <<<天空>>>
>>
>> 我爱天空和大地
>> 
>
>Org doesn't support mid-word radio targets. Is there any strong reason
>to make a case for Chinese? What about other languages?
>
>


Because Chinese need no space between words :-), for example:

我不知道这个事情到底对不对，你觉得对就对，不对就不对。

I have updated the patch adviced by Eric Abrahamsen:




>Regards,
>
>-- 
>Nicolas Goaziou


0001-Let-radio-target-works-well-with-Chinese.patch
Description: Binary data

Re: [O] [PATCH] Let radio target works well with Chinese

[tumashu]

At 2019-02-26 03:50:37, "Eric Abrahamsen"  wrote:
>Emilio Francesquini  writes:
>
>> Hello,
>>
>>> <<<天空>>>
>>> >
>>> > 我爱天空和大地
>>> > 
>>>
>>> Org doesn't support mid-word radio targets. Is there any strong reason
>>> to make a case for Chinese? What about other languages?
>>>
>>
>> My knowledge in Chinese is rather limited, but if it is a little like
>> Japanese the problem is that those languages do not use spaces to separate
>> words.
>>
>> I found myself in the same situation writing radio targets in Japanese...
>> My workaroud was to insert artificial spaces as needed... :/
>
>I've gotten this information (does-space-separate-words) for specific
>characters before using either of these two methods:
>
>(aref (char-category-set ?b) ?|) => nil
>(aref (char-category-set ?中) ?|) => t
>
>(aref fill-nospace-between-words-table?b) => nil
>(aref fill-nospace-between-words-table ?中) => t
>
>| is the category character for "line breakable". Perhaps adding "\c|"
>to the regexp would DTRT?

Seem to be a good idea :-)

>
>Eric
>

[O] [Suggest] Add a command org-attach-sync-all

[tumashu]

I alway forgot to run org-attach-sync when I manual update task's attach dir,
suggest add a sync all command like below:



``` 

(defun org-attach-sync-all ()
(interactive)
(org-map-entries #'org-attach-sync)
(org-align-all-tags))




```

Re: [O] FW: [RFC] Link-type for attachments, more attach options

[tumashu]

Hello, this feature seem to be very useful, what is this patch status?






At 2018-10-21 15:53:38, "Gustav Wikström"  wrote:


Hi,

 

I’ve attached a patch with some suggested additions to org-attach. Patch 
comments below. Please review.

 

Kind regards

Gustav

___

Patch comments:

* Add new linktype "attached" for attachments

 

A new linktype "attached" is added in order to reduce link-duplication

when wanting to link to files in attached folders of nodes. This works

for both ID-based attachments and ATTACH_DIR.  Inline images will

trigger also for attachments, as well as search-decorations in the

links.  The goal is to make the functionality for attached-links

mirror file-links.

 

* Add further options for ATTACH_DIR

 

When working with ATTACH_DIR there are now a couple of new options available:

- org-attach-dir-inherit-by-default

- org-attach-dir-create-if-not-exist

- org-attach-dir-relative

 

Descriptions of them can be found in the commit for each new customization.

 

* Documentation in org-manual

 

Org-manual is updated with the new link-type as well as some minor

cleanup in the documentation related to external links and attachments.

 

 

Re: [O] BUG: org tag can align proper when tag is Chinese.

[tumashu]

At 2018-05-07 21:22:34, "Nicolas Goaziou" <m...@nicolasgoaziou.fr> wrote:
>Hello,
>
>tumashu <tuma...@163.com> writes:
>
>> 1.  [:alnum:] can not match Chinese char,  what about add [:multibyte:] ?
>
>What about :
>
>  [:alnum:] + [:multibyte:] -> [:word:]



 I found [:alnum:] can match Chinese 

 (string-match-p "[[:alnum:]]" "@@@你好")  => 3

But using [:word:] may better, in my opinion.

the real problem is that my org-head face's height is not 1.0,

Sorry 


>Could you test this change?
>
>Regards,
>
>-- 
>Nicolas Goaziou

Re: [O] BUG: org tag can align proper when tag is Chinese.

[tumashu]

>
>Could you test this change?

Seem to work!


Another problem I have found is that: when having Chinese char, 
(window-text-width) is not a stable method, but I do
not know how to fix it.
```
(defun org-agenda-align-tags ( line)
  "Align all tags in agenda items to `org-agenda-tags-column'."
  (let ((inhibit-read-only t)
(org-agenda-tags-column (if (eq 'auto org-agenda-tags-column)
(- (window-text-width))
  org-agenda-tags-column))
...
)
```

[O] BUG: org tag can align proper when tag is Chinese.

[tumashu]

1.  [:alnum:] can not match Chinese char,  what about add [:multibyte:] ?
```
(defun org--align-tags-here (to-col)
 ...
    (if    (or (not (looking-at ".*?\\([ \t]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ 
\t]*$"))

 ...
)

(defun org-agenda-align-tags ( line)
 ...
  (while (re-search-forward "\\([ \t]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ \t]*$"
 ...

)
```

Re: [O] [SOLVED] org-attach provide org-store-link like link for org-insert-link

[tumashu]

At 2018-05-05 13:14:10, "stardiviner"  wrote:
>
>stardiviner  writes:
>
>> I used a lot with org-attach to insert files like images, small PDF
>> files, and audio. Every time I attached one file, I have to manually
>> link to that attachment file.
>>
>> Can org-attach provide link directly after finished attaching? So user
>> can press [C-c C-l] (org-insert-link) directly.
>
>After check out org-attach.el source code. I found option
>`org-attach-store-link-p`. This is what I want.

A very good tip, thanks!
>
>--
>[ stardiviner ] don't need to convince with trends.
>   Blog: https://stardiviner.github.io/
>   IRC(freenode): stardiviner
>   GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

[O] Should wip-cite branch be merged to master?

[tumashu]

There is a package which support wip-cite: 
https://github.com/andras-simonyi/citeproc-org, should wip-cite branch
be merged to master now?

Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.

[tumashu]

At 2018-04-14 17:42:27, "tumashu" <tuma...@163.com> wrote:
>
>
>
>
>
>
>
>
>
>
>At 2018-04-14 15:44:00, "Nicolas Goaziou" <m...@nicolasgoaziou.fr> wrote:
>>Hello,
>>
>>tumashu  <tuma...@163.com> writes:
>>
>>> I do not know why must save-buffer, may be for  information safe :-)
>>
>>If there is no objection, I suggest to simply remove this call to
>>`save-buffer' instead of introducing a new variable.
>>
>
>Agree this idea,  If user want to save-buffer when capture finish, they can
>add save-buffer to org-capture-after-finalize-hook  or just type C-x C-s
>
>>Regards,
>>
>>-- 
>>Nicolas Goaziou0x80A93738


0001-org-capture-Do-not-save-buffer-when-run-org-capture-.patch
Description: Binary data

Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.

[tumashu]

At 2018-04-14 15:44:00, "Nicolas Goaziou" <m...@nicolasgoaziou.fr> wrote:
>Hello,
>
>tumashu  <tuma...@163.com> writes:
>
>> I do not know why must save-buffer, may be for  information safe :-)
>
>If there is no objection, I suggest to simply remove this call to
>`save-buffer' instead of introducing a new variable.
>

Agree this idea,  If user want to save-buffer when capture finish, they can
add save-buffer to org-capture-after-finalize-hook  or just type C-x C-s

>Regards,
>
>-- 
>Nicolas Goaziou0x80A93738

Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.

[tumashu]

At 2018-04-12 21:22:21, "Nicolas Goaziou" <m...@nicolasgoaziou.fr> wrote:
>Hello,
>
>tumashu <tuma...@163.com> writes:
>
>> I use org-capture to capture text to a file of my mobile phone
>> with the help of tramp and termux's sshd, the save buffer is very
>> slow, so I want to org-capture-finalize just update buffer, and
>> I save buffer manually when need.
>
>Thank you. Comments follow.
>
>> By the way, can we contribute org-mode with the help of PR feature in
>> code.orgmode.org?
>
>AFAIC, I'd rather deal with email than with a web interface. However,
>Bastien accepted PR from code.orgmode.org in the past.
>
>The problem with PR in code.orgmode.org is that the discussion around
>the patch happens somewhere else than on the ML.
>
>> +(defcustom org-capture-finalize-save-buffer t
>> +  "When nil, org-capture-finalize will not save target file's buffer."
>> +  :group 'org-capture
>> +  :version "24.1"
>> +  :type 'boolean)
>
>The :version value is incorrect. Also, it is missing ":safe #'booleanp".
>

:version 26.1 ? or 27.0 ?


>>  (defcustom org-capture-bookmark t
>>"When non-nil, add a bookmark pointing at the last stored
>>  position when capturing."
>> @@ -791,7 +797,10 @@ captured item after finalizing."
>>  (org-encrypt-entry)))
>>  
>>  ;; Kill the indirect buffer
>> -(save-buffer)
>> +(if org-capture-finalize-save-buffer
>> +(save-buffer)
>> +  (message "The capture target file is not auto saved, please save it 
>> manually."))
>
>Would it make sense to simply not call `save-buffer' in all cases?
>Saving buffer after a capture is rather opinionated.

I do not know why must save-buffer, may be for  information safe :-)

>
>
>Regards,
>
>-- 
>Nicolas Goaziou

[O] [PATCH] org-capture: Add a custom to control save target file or not.

[tumashu]

I use org-capture to capture text to a file of my mobile phone
with the help of tramp and termux's sshd, the save buffer is very
slow, so I want to org-capture-finalize just update buffer, and
I save buffer manually when need.


By the way, can we contribute org-mode with the help of PR feature in 
code.orgmode.org?


0001-org-capture-Add-a-custom-to-control-save-target-file.patch
Description: Binary data

Re: [O] ANNOUNCE: GNU Hyperbole 6.0.1 for Emacs 24.4 - 25 is released

[tumashu]

great comment

在 2016-07-30 00:25:12，"aditya siram"  写道：

I never used Hyperbole back in the day so this is all fresh for me. I am also 
an avid org-mode user. The following feedback is based on about 48 hours of 
usage.


Hyperbole is a suite of tools. One of them is an outliner that overlaps quite a 
bit with org-mode. It has some interesting features like being able to link 
individual paragraphs as opposed to just headings/sub-headings but in most 
cases org-mode is further along.

But there are other tools in Hyperbole that might interest you including 
Acme-like string execution. For example if you do M-RET on the word README it 
automatically jumps to README without having to go through the rigamarole or 
creating a link in org-mode.


One of the nicest things about Hyperbole is that it's available everywhere. 
Org-mode is a mode and its features are only available in *.org files. For 
instance if you dropped into `eshell` or `ansi-term` and did `ls`, you can move 
point to any of the directory's contents, do M-RET (or Shift-Button2) and jump 
to that file. And that's just one example. Note that this means that all 
Hyperbole functionality is available in *.org files as well. To me, except for 
the Hyperbole outliner, that makes complementary not conflicting. It's 
Hyperbole *and* org-mode, not Hyperbole vs. org-mode.



Additionally, off the bat, I found it very well documented and for me that's a 
proxy for the quality of a package and the maintainer, Robert Weiner is quite 
responsive and really seems to want Hyperbole to take off. There's plenty more 
functionality that I haven't uncovered yet but due to ease of installation and 
quality of documentation digging into it is actually fun; much more 
discoverable than org-mode which has become this giant bag of random directives.


Hyperbole, even though it is old, feels like it is in its second infancy 
meaning it is open to change based on community feedback. As a practical note, 
once you install it doing C-h h d d will fire up a nice Demo which I is think 
is more fun than watching a screencast.


-deech




On Fri, Jul 29, 2016 at 10:54 AM, Kaushal Modi  wrote:

Actually it will be even more awesome if you can record a short video/GIF 
screencast demonstrating what hyperbole does compared to org mode. Or in 
general how you would use hyperbole.


Thanks.


On Fri, Jul 29, 2016 at 11:52 AM Adam Porter  wrote:

Charles Philip Chan  writes:

> Wow, blast from the past. I remember using older versions of Hyperbole
> fondly and still miss it. Thank you for updating it. I look forward to
> using it. :-)

Charles, could you explain a little bit how it compares to Org?  I read
the thread on /r/emacs and looked at the wiki, but I'm still not sure
how it compares to or complements Org.



--


Kaushal Modi

[O] [BUG] Error running timer ‘org-element--cache-sync’: (wrong-type-argument hash-table-p nil)

[tumashu]

1. GNU Emacs 25.0.95.1 (i686-w64-mingw32) of 2016-06-13
2. org-20160704


#+BEGIN_COMMENT
(let ((buffer-name "*Test*"))
  (with-output-to-temp-buffer buffer-name
(set-buffer buffer-name)
(when (featurep 'org)
  (org-mode))
(setq truncate-lines 1)
(setq cursor-type nil)
(insert "This is a test")))
#+END_COMMENT

The debug info:

#+BEGIN_COMMENT
Debugger entered--Lisp error: (wrong-type-argument hash-table-p nil)
  clrhash(nil)
  org-element--cache-sync(#)
  apply(org-element--cache-sync #)
  timer-event-handler([t 0 0 59 nil org-element--cache-sync (#) idle 99])
Debugger entered--Lisp error: (wrong-type-argument hash-table-p nil)
  clrhash(nil)
  org-element--cache-sync(#)
  apply(org-element--cache-sync #)
  timer-event-handler([t 0 0 59 nil org-element--cache-sync (#) idle 99])

#+END_COMMENT

Re: [O] [PATCH] ob-sql.el: Support sqlcmd and cygwin environment

[tumashu]

You can use sqsh to connect MS-sql too, more info you can see: 
https://github.com/tumashu/sql-mssql




At 2016-06-16 14:04:26, "Xi Shen" <davidshe...@gmail.com> wrote:

Hi Nicolas,


Please take a look at the updated patch. Changes:


- add ORG-NEWS entry
- add function declaration
- add input file template for `mssql' engine to remove the "affected rows" tail



On Thu, Jun 16, 2016 at 12:49 AM Nicolas Goaziou <m...@nicolasgoaziou.fr> wrote:

Hello,

Xi Shen <davidshe...@gmail.com> writes:

> I suppose I should put the news entry to ./etc/ORG-NEWS file, but into
> which version? I created below entry, please take look and let me know
> where do you want me to put it.

I'd say

  Version 9.0 > New features > Babel

or

  Version 9.0 > Miscellaneous

> *** Improved support to Microsoft SQL Server in =ob-sql.el=
> =ob-sql.el= library removes support to the ~msosql~ engine which uses
> the deprecated =osql= command line tool, and replaces it with ~mssql~
> engine which uses the =sqlcmd= command line tool.  Use with properties
> like this:
>
> #+BEGIN_EXAMPLE
>  :engine mssql
>  :dbhost 
>  :dbuser 
>  :dbpassword 
>  :database 
> #+END_EXAMPLE
>
> If you want to use the *trusted connection* feature, omit *both* the
> =dbuser= and =dbpassword= properties and add =cmdline -E= to the
> properties.
>
> If your Emacs is running in a Cygwin environment, the =ob-sql.el=
> library can pass the converted path to the =sqlcmd= tool.

It looks good.

> I checked the code and it does not quote the arguments for me. It is a safe
> manner in Windows to always quote the path. So I will keep it.

Fair enough.

> I have a question. Currently the table generated by mssql engine has the
> "affected rows" append to the end, like this.
>
>   |  memberid | username | xx   | flags |
>   |---+--+--+---|
>   | 1 | GPL  | Indo | NULL  |
>   | 2 | GPL  | Indo | NULL  |
>   |   |  |  |   |
>   | (2 rows affected) |  |  |   |
>
> I personally prefer to remove it. Do you or the org community has a
> preference about this? Maybe I should keep the behavior align with other
> engines?

I lean towards removing it, too. I doesn't give useful feedback. We can
always insert it back later if it introduces unwanted side-effects.


Thank you.


Regards,

--
Nicolas Goaziou

--



Thanks,
David S.

Re: [O] capture with iceweasel/firefox -- nothing works

[tumashu]

https://github.com/tumashu/org-capture-pop-frame

you can try above package


--
发自我的网易邮箱手机智能版


在 2016-06-04 09:23:09，"Samuel Wales" <samolog...@gmail.com> 写道：
>over many years, i have been trying to get org-protocol (or
>anything similar) to work, and it is not working reliably.
>
>intermittently, it says there is a greedy protocol.  the
>success rate of capturing is around 50% maybe.  when it is not
>working, it never works.  i have
>noticed no correlation with anything that could cause this.
>
>sometimes it captures bogus text when i just want the link,
>but i don't care about that.  at least it copied the link.
>
>i've tried:
>
>  1) org-capture firefox extension
>  2) a bookmark like this
> - 
> javascript:location.href%20=%20'org-protocol://capture-html://w/'%20+%20encodeURIComponent(location.href)%20+%20'/'%20+%20encodeURIComponent(document.title)%20+%20'/'%20+%20encodeURIComponent(function%20()%20{var%20html%20=%20"";%20if%20(typeof%20document.getSelection%20!=%20"undefined")%20{var%20sel%20=%20document.getSelection();%20if%20(sel.rangeCount)%20{var%20container%20=%20document.createElement("div");%20for%20(var%20i%20=%200,%20len%20=%20sel.rangeCount;%20i%20<%20len;%20++i)%20{container.appendChild(sel.getRangeAt(i).cloneContents());}%20html%20=%20container.innerHTML;}}%20else%20if%20(typeof%20document.selection%20!=%20"undefined")%20{if%20(document.selection.type%20==%20"Text")%20{html%20=%20document.selection.createRange().htmlText;}}%20var%20relToAbs%20=%20function%20(href)%20{var%20a%20=%20document.createElement("a");%20a.href%20=%20href;%20var%20abs%20=%20a.protocol%20+%20"//"%20+%20a.host%20+%20a.pathname%20+%20a.search%20+%20a.hash;%20a.remove();%20return%20abs;};%20var%20elementTypes%20=%20[['a',%20'href'],%20['img',%20'src']];%20var%20div%20=%20document.createElement('div');%20div.innerHTML%20=%20html;%20elementTypes.map(function(elementType)%20{var%20elements%20=%20div.getElementsByTagName(elementType[0]);%20for%20(var%20i%20=%200;%20i%20<%20elements.length;%20i++)%20{elements[i].setAttribute(elementType[1],%20relToAbs(elements[i].getAttribute(elementType[1])));}});%20return%20div.innerHTML;}());
>  3) a bookmark like this
> - 
> javascript:location.href='org-protocol://capture://L/'+encodeURIComponent(location.href)+'/'+encodeURIComponent(document.title)+'/'+encodeURIComponent(window.getSelection())
>  4) i know there's a new one that is supposed to capture
> format better (so you don't end up with a single
> paragraph when there were several paragraphs).  that
> sounds wonderful!  however, i am limited in computer
> use (4 minutes at a time), so i don't know if it is
> worth my trying or not.  i have to use those 4 minutes responsibly.
>  5) i followed various instructions
>
>i currently using iceweasel 38.8.0 (debian jessie) and
>emacs-version "24.4.1".
>
>i understand elisp and org.
>
>however, i don't understand javascript or org-protocol's
>internal concepts.  i am limited in concentration ability,
>so this could be a problem.  i am also hazy on how to set up
>a bookmark, but i somehow managed to do it twice.
>
>===
>
>i am very often physically unable to use a keyboard.  during
>these times i am often able to use a pointing device (2
>mouses, one for clicking and one for moving).
>
>i am often using firefox (iceweasel) and want to capture
>things to org using only the mouse.
>
>that's why i want this feature to work so much.
>
>===
>
>i want to use org-capture extension or similar so that i can
>copy snippets of text like this:
>
>  * [[link][descr]]
>  text that i selected
>  ---
>
>(the --- indicates that it came from iceweasel, and is not something i wrote.)
>
>or just the plain link like this if nothing is selected:
>
>  * [[link][descr]]
>
>i have this working.  it is just unreliable, failing randomly at random times.
>
>(note: i don't want emacs to pop up and there should be no keyboard
>interaction.  useful if emacs switches to the buffer it is saved to,
>however.  i have all that stuff taken care of in my elisp.  that part
>i understand and can fix by myself.)
>
>===
>
>i am stuck on this.
>
>after all that long-windedness, my question is this:
>
>  *what is the most reliable set of instructions or code to
>  get iceweasel to work with org?*
>
>i'd be grateful for any useful hints.
>
>thanks.
>
>
>samuel
>
>===
>
>here are just 2 of the many elisp-side things i tried over
>the years to get this to work.  elisp i can handle.
>
>  (setq org-capture-templates
>(append
> org-capture-templates
> `(
>   ("p" "Protocol&qu

Re: [O] (V8) [PATCH] New feature: Use dvisvgm to preview latex formular

[tumashu]

  `((?b . ,(shell-quote-argument base-name))
   (?f . ,(shell-quote-argument full-name))
  (?o . ,(shell-quote-argument out-dir))


What about add a  spec to  output-file, some commands need this information.
I will edit my diff tonight and sent to org-mode mailling list as far as 
possible.

Re: [O] (v6) [PATCH] New feature: Use dvisvgm to preview latex formular

[tumashu]

If we need 4 cmmand to convert test.dvi to test.png
1. cmd1 test.dvi  test.a
2. cmd2 test.a test.b
3. cmd4 test.b test.png

does it work correctly?  can %b.a convert to  text.a ? 
("cmd1 %b.dvi %b.a"
 "cmd2 %b.a %b.b"
"cmd3  %b.b %b.png")

if it works properly,  i suggest  merge org-compile-file feature first, i will 
rebase my patch to it before merge.

Re: [O] (v6) [PATCH] New feature: Use dvisvgm to preview latex formular

[tumashu]

i see your mean, i think org-compile-file can do more thing, for example: 
handle dvipng or dvisvgm, 

what i need to know is the different of call-process and run shell command.  
can we use run shell command instead of call-process in converting dvi to png?

special string need to do more work, i think.






--
发自我的网易邮箱手机智能版


在 2016-05-17 05:17:45，"Nicolas Goaziou"  写道：
>Hello,
>
>"Feng Shu"  writes:
>
>> This is my modified patch (v6), fix the problems you stated. please review
>> again, thank!
>
>Thank you. Comments follow.
>
>> From 29760e5c5876fb6b772f7a6004b7160bc06efba8 Mon Sep 17 00:00:00 2001
>> From: Feng Shu 
>> Date: Sat, 14 May 2016 22:42:53 +0800
>> Subject: [PATCH] New feature: Use dvisvgm to preview latex formular
>>
>> * ox-latex.el (org-latex-pdf-process): org-latex-pdf-process can be a
>>   configure generator (a plist with :generator keyword).
>> (org-latex-preview-process): new variable, which is used to process
>>  latex snippet.
>> (org-latex-compile): Add a new optional argument: extra-info.
>
>As discussed in another message, I don't think we should mess with
>`org-latex-compile'. Instead, we could factor out the needed part in
>`org-latex-compile' and make it a generic function. Then we can
>introduce a new function to specifically handle previewing related
>compilation.
>
>Note that I'm not asking you to implement the factoring out part in your
>patch, but to tell me if the following would fulfill your needs for
>`org-create-formula-image'. I'm sending its docstring again.
>
>  (defun org-compile-file (source process extension  spec log-buffer)
>"Compile a SOURCE file using PROCESS.
>
>  PROCESS is either a function or a list of shell commands, as
>  strings.
>
>  If PROCESS is a function, it is called with a single argument:
>  SOURCE file.  It must create a file with the same base name and
>  directory as SOURCE, but using extension.
>
>  If it is a list of commands, each of them is called using
>  `shell-command'.  By default, in each command, %b, %f and %o are
>  replaced, respectively, with SOURCE base name, SOURCE full name
>  and SOURCE directory.  It is possible, however, to use different
>  place-holders by specifying them in optional argument SPEC.  In
>  this case, SPEC should be an alist (STRING REPLACEMENT-STRING).
>
>  When PROCESS is a list of commands, optional argument LOG-BUFFER
>  can be set to a buffer or a buffer name.  `shell-command' then
>  uses it as an output buffer, which may be used for collecting
>  errors.
>
>  `default-directory' is set to SOURCE directory during the whole
>  process.
>
>  Generated file is expected to use the same directory and base
>  name as SOURCE, and end with EXTENSION.  Return its filename or
>  raise an error if it wasn't generated upon executing PROCESS."
>...)
>
>
>> +If you have a working @LaTeX{} installation and @file{dvipng}, 
>> @file{dvisvgm}
>> +or @file{convert} installed@footnote{These are respectively available at
>> +@url{http://sourceforge.net/projects/dvipng/}, 
>> @url{http://dvisvgm.bplaced.net/}
>> +and from the @file{imagemagick} suite. Choose the converter by setting the 
>> variable
>
>You need to use two spaces to separate sentences.
>
>>  +(defcustom org-latex-to-image-backends
>
>You could remove it `org-preview-latex-backends' since it doesn't belong
>to the "org-latex" namespace.
>
>> +dvisvgm Process the LaTeX fragments to dvi/xdv file, then convert
>> +dvi/xdv files to svg files using dvipng.
>
>You probably mean "using dvisvgm".
>
>> +Org mode can use some external commands to generate TeX snippet's image for
>> +previewing or inserting into HTML files, e.g. dvipng, dvisvgm or imagemagick
>> +this variable tells `org-create-formula-image' how to use external commands.
>
>or imagemagick.  This variable tells...
>
>> +  :class  symbol, this setting may be useful in future.
>
>Meanwhile, I suggest to remove it, unless you have a clear plan in mind.
>
>> +  :name   string, the backend's name.
>> +  :programs   list of strings, required programs.
>> +  :messagestring, message it when required program can't be 
>> found.
>
>required programs
>
>> +  :color  symbol, if set to `latex', LaTeX \"xcolor\" macro is 
>> used
>> +  to deal with background and foreground color of image,
>> +  if set to `divpng', dvipng style background and 
>> foregroud color
>> +  format will be generated, you should use them in 
>> command options
>> +  with special string: \"%fg\"% and \"%bg%\".
>
>are generated; you should used them in ... with special strings: ...
>
>> +  :size-adjustcons of numbers, the car element is used to adjust 
>> latex image
>> +  size showed in buffer and the cdr element is for html 
>> file.
>> +

Re: [O] (version 3) [PATCH] New feature: Use dvisvgm to preview latex formular

[tumashu]

--
发自我的网易邮箱手机智能版


在 2016-05-16 21:18:20，"Nicolas Goaziou"  写道：
>Hello,
>
>"Feng Shu"  writes:
>
>> I suggest to add (:generator my-generator-function) style configure
>> to `org-latex-pdf-process', it is simple and powerful feature, we
>> can use this feature to switch latex commands dynamicially, for example:
>>
>> (defun my-latex-pdf-process-generator (texfile snippet extra-info)
>>   (cond
>>(() ()
>>(() ()
>>
>> although we can set org-latex-pdf-process to a function to do the same work,
>> but this function is hard to write as org-latex-compile, it may only
>> useful for developer instead of user
>>
>> caller-info argument is for the above feature.
>
>I understand the need to extend `org-latex-pdf-process'. However this
>isn't a good way to look at it. In fact, it makes little sense to load
>the whole export framework when you're only after displaying a LaTeX
>snippet in the current buffer.
>
>I think a better approach would be to create a generic tool to compile
>a file to another format, e.g. `org-compile-file'. It would take a command
>(as a list of strings or a function) and apply it to the source file
>name. Then it would check if the output file was produced. Optionally,
>it would allow to create a buffer so as to retrieve error messages.
>
>Then, e.g., `org-latex-compile' or `org-preview-generate-image', could
>extend this function, i.e., handle specific variables (e.g.,
>`org-latex-pdf-process') and call it with appropriate arguments.
>
>As example, here's a proof of concept for `org-compile-file' and
>`org-latex-compile'.
>
>  (defun org-compile-file (source process extension  spec log-buffer)
>"Compile a SOURCE file using PROCESS.
>
>  PROCESS is either a function or a list of shell commands, as
>  strings.
>
>  If PROCESS is a function, it is called with a single argument:
>  SOURCE file.  It must create a file with the same base name and
>  directory as SOURCE, but using extension.
>
>  If it is a list of commands, each of them is called using
>  `shell-command'.  By default, in each command, %b, %f and %o are
>  replaced, respectively, with SOURCE base name, SOURCE full name
>  and SOURCE directory.  It is possible, however, to use different
>  place-holders by specifying them in optional argument SPEC.  In
>  this case, SPEC should be an alist (CHARACTER REPLACEMENT-STRING).
>
>  When PROCESS is a list of commands, optional argument LOG-BUFFER
>  can be set to a buffer or a buffer name.  `shell-command' then
>  uses it as an output buffer, which may be used for collecting
>  errors.
>
>  `default-directory' is set to SOURCE directory during the whole
>  process.
>
>  Return output file or raise an error if it wasn't generated upon
>  executing PROCESS."
>(let* ((base-name (file-name-sans-extension (file-name-nondirectory 
> source)))
>(full-name (file-truename source))
>(out-dir (file-name-directory source))
>;; Properly set working directory for compilation.
>(default-directory (if (file-name-absolute-p source)
>   (file-name-directory full-name)
> default-directory))
>(time (current-time)))
>  (save-window-excursion
>(pcase process
>  ((pred functionp) (funcall process (shell-quote-argument source)))
>  ((pred consp)
>   (let ((log (and log-buffer (get-buffer-create log-buffer)))
> (spec (or spec
>   `((?b ,(shell-quote-argument base-name))
> (?f ,(shell-quote-argument full-name))
> (?o ,(shell-quote-argument out-dir))
> (dolist (command process)
>   (shell-command (format-spec command spec) log
>  (t (error "No valid command to process %S" source)))
>;; Check for process failure.
>(let ((output (concat out-dire base-name extension)))
>  (when (or (not (file-exists-p output))
>;; Only compare times up to whole seconds as some
>;; file-systems (e.g. HFS+) do not retain any finer
>;; granularity.
>(time-less-p (cl-subseq (nth 5 (file-attributes output)) 0 
> 2)
> (cl-subseq time 0 2)))
>(error (format "File %S wasn't produced" output)))
>  output
>
>  (defun org-latex-compile (texfile)
>"Compile a TeX file.
>
>  TEXFILE is the name of the file being compiled.  Processing is
>  done through the command specified in `org-latex-pdf-process'.
>
>  Return PDF file name or an error if it couldn't be produced."
>(message "Processing LaTeX file %s..." texfile)
>(let* ((base-name (file-name-sans-extension (file-name-nondirectory 
> texfile)))
>(full-name (file-truename texfile))
>(compiler (or (with-temp-buffer
>(save-excursion (insert-file-contents 

Re: [O] latex fragment png's size too small

[tumashu]

The problem is that the pic is too small and nearly can not see the words in 
the picture, it will force user config it, if we use a larger pic, it can work 
although it is ugly
在 2016-05-14 16:56:15，"Nicolas Goaziou" <m...@nicolasgoaziou.fr> 写道：
Hello,

tumashu <tuma...@163.com> writes:

> The preview png of latex fragment seem to small, what about change
> default `org-format-latex-options'  :scale from 1.0 to 2.0?

As a data point, I use :scale 1.2. A factor of 2 may be too large for
some users.

In any case, the manual already highlights it:

 You can customize the variable ‘org-format-latex-options’ to
  influence some aspects of the preview.  In particular, the ‘:scale’ (and
  for HTML export, ‘:html-scale’) property can be used to adjust the size
  of the preview images.

Since there may not be a more reasonable default value, the best thing
to do could be to leave it up to the user to set his own factor.

WDYT?


Regards,

-- 
Nicolas Goaziou

[O] latex fragment png's size too small

[tumashu]

The preview png of latex fragment seem to small, what about change default 
`org-format-latex-options'  :scale from 1.0 to 2.0?

[O] Use dvisvgm to preview latex fragments

[tumashu]

I find a new tool: dvisvgm (https://github.com/mgieseki/dvisvgm)  ,which we can 
use it to preview latex fregments, it can deal with
xetex's xdv file as well (it will available in texlive2016).

The questions are:
1.  which path we should use:   "dvi/xdv -> svg" or "dvi/xdv -> svg -> png" ?
2. if we use the first path, how to deal with 
org-latex-preview-ltxpng-directory?  should we rename it to 
org-latex-preview-ltximg-directory or
   org-latex-preview-ltxpic-directory ?
 

[O] [question] How to filter a head based head name?

[tumashu]

The below is an example, I want to ignore *head1* and *its content* when
export to html, but for some reason I can't add tags to head, How to
solve this problem?

If I want to rename *head2* to *new-head2*, how to do?

#+BEGIN_ORG
* head1
  content1
  
* head2
  content2
  
* head3
  content3
#+END_ORG

Thanks!

Re: [O] #+begin_src R :results output drawer doesn't work.

[tumashu]

wheniremoverecentfcatchfile,it'sok.thank.---Original---From: Aaron Ecayaarone...@gmail.comDate: 2014/08/13 14:19:01To: Feng Shutuma...@gmail.com;emacs-orgmodeemacs-orgmode@gnu.org;Subject: Re: [O] #+begin_src R :results output drawer doesn't work.Hi Feng,

2014ko abuztuak 9an, Feng Shu-ek idatzi zuen:
 
 #+begin_src R :results output drawer
 1
 2
 #+end_src
 
 #+RESULTS:
 : 2


Like Eric, I cannot reproduce this behavior.  Can you send us the output
of the following code block, to check the exact version of org that is
giving you this unexpected result?

#+BEGIN_SRC emacs-lisp
  (org-version nil t)
#+END_SRC

Thanks,

-- 
Aaron Ecay

Re: [O] [PATCH] Adding Simplified Chinese(UTF-8) translation for org-exp

[tumashu]

Today, I test Simplified Chinese(UTF-8) translation for org-exp.el again,
I find that zh_CN  is  used by *xml:lang* and *lang*
#+begin_example
html xmlns=http://www.w3.org/1999/xhtml; lang=zh_CN xml:lang=zh_CN
#+end_example


It should be:
#+begin_example
html xmlns=http://www.w3.org/1999/xhtml; lang=zh-CN xml:lang=zh-CN
#+end_example
[[http://www.w3.org/International/articles/bcp47/]] 


Changes in master
Modified   lisp/org-exp.el
diff --git a/lisp/org-exp.el b/lisp/org-exp.el
index a2f0cfc..3f52be0 100644
--- a/lisp/org-exp.el
+++ b/lisp/org-exp.el
@@ -205,8 +205,8 @@ This option can also be set with the +OPTIONS line, e.g. 
\-:nil\.
 (ru #1040;#1074;#1090;#1086;#1088;  
#1044;#1072;#1090;#1072;  
#1057;#1086;#1076;#1077;#1088;#1078;#1072;#1085;#1080;#1077; 
#1057;#1085;#1086;#1089;#1082;#1080;)
 (sv Fouml;rfattare Datum Inneharing;ll Fotnoter)
 ;; Use numeric character entities for proper rendering of non-UTF8 
documents
-;; (zh_CN 作者 日期 目录 脚注)
-(zh_CN #20316;#32773; #26085;#26399; #30446;#24405; 
#33050;#27880;))
+;; (zh-CN 作者 日期 目录 脚注)
+(zh-CN #20316;#32773; #26085;#26399; #30446;#24405; 
#33050;#27880;))
   Terms used in export text, translated to different languages.
 Use the variable `org-export-default-language' to set the language,
 or use the +OPTION lines for a per-file setting.

[O] [PATCH] Adding Simplified Chinese(UTF-8) translation for org-exp

[tumashu]

---
 lisp/org-exp.el |3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/lisp/org-exp.el b/lisp/org-exp.el
index a1102a8..229d83c 100644
--- a/lisp/org-exp.el
+++ b/lisp/org-exp.el
@@ -200,7 +200,8 @@ This option can also be set with the +OPTIONS line, e.g. 
\-:nil\.
 (nn Forfattar  Dato  Innhald Fotnotar)  ;; nn = Norsk (nynorsk)
 (pl Autor  Data Spis tre#x015b;ci  Przypis)
 (ru Автор  Дата  Содержание Сноски)
-(sv Fouml;rfattare Datum Inneharing;ll Fotnoter))
+(sv Fouml;rfattare Datum Inneharing;ll Fotnoter)
+(zh_CN 作者 日期 目录 脚注))
   Terms used in export text, translated to different languages.
 Use the variable `org-export-default-language' to set the language,
 or use the +OPTION lines for a per-file setting.
-- 
1.7.9.1