York Zhao writes:
[...]
> Seems to be a reasonable solution to me. So would you go ahead and make the
> change, or, would more people need to agreed on this solution?
If there are no objections within a few days, I'll apply the following
patch to maint.
-- >8 --
> Yeah, org-store-link overloads ARG
Exactly!
> I think that, when negating org-context-in-file-links, the function should
> check whether a single C-u was given rather than just checking if ARG is
> non-nil.
Seems to be a reasonable solution to me. So would you go ahead and make the
change,
On Sat, 20 May 2017, John Kitchin wrote:
If I run this block I get test as a result, but all its properties have
been stripped.
#+BEGIN_SRC emacs-lisp :results drawer
(propertize "test" 'font-lock-face '(:foreground "red") 'help-echo
"tooltip")
#+END_SRC
#+RESULTS:
:RESULTS:
test
:END:
Does
If I run this block I get test as a result, but all its properties have
been stripped.
#+BEGIN_SRC emacs-lisp :results drawer
(propertize "test" 'font-lock-face '(:foreground "red") 'help-echo
"tooltip")
#+END_SRC
#+RESULTS:
:RESULTS:
test
:END:
Does anyone know where this happens and if it can
York Zhao writes:
> However, the biggest problem I'm having now is that once I loaded
> org-git-link.el, I'm forced to always store links linking to git repository
> which is not always I want because I also need to be able to store links
> linking to the files in the
Hello,
Hendrik Tews writes:
> in section 7.5.1.2 Column attributes, the manual says
>
> Numbers are right-aligned when a format specifier with an
> explicit width like ā%5dā or ā%5.1fā is used.
>
> However, I see something similar to
>
>5.0 | * a|
>
Hi org-mode developers,
Recently I found it very useful to being able to store links linking to
source code in git repository. I used org-git-link.el for this purpose and
it works well.
However, the biggest problem I'm having now is that once I loaded
org-git-link.el, I'm forced to always store
Hi,
Nicolas Goaziou writes:
> Hello,
>
> Tim Stewart writes:
>
>> * lisp/org.el (org--get-expected-indentation): Fix indentation within
>> lists after blocks that support a special editing environment.
>>
>> Testing shows that the indentation within
Hello,
"H.M. Pham" writes:
> I just downloaded org-plus-contrib and my customizde capture stopped
> working. The function org-set-tags-to is different than the org
> package. The let form shows up in the org-plus-contrib.
>
> (when (let ((case-fold-search nil)) < i
> * How to add ASME?
> I want to know if there is a way to add the ASME database to org-ref.
>
> I found this: https://github.com/jkitchin/org-ref/issues/148 which hints
> me in the right direction, but I don't know how to make it work.
>
> I am trying with this article:
>
I suddenly am unable to open my org agenda. Invoking ~C-a~ and selecting
any agenda command results in
~org-refresh-stats-properties: Stack overflow in regexp matcher~
The debug trace looks like:
#+BEGIN_SRC
Debugger entered--Lisp error: (error "Stack overflow in regexp matcher")
I just downloaded org-plus-contrib and my customizde capture stopped
working. The function org-set-tags-to is different than the org
package. The let form shows up in the org-plus-contrib.
(when (let ((case-fold-search nil)) < i think this line is wrong
(looking-at
Dear Dr. Kitchin and Org-mode mailing list,
I write to you, because I could not find a mailing list for org-ref.
Thanks for your time.
I am just starting to use org-ref with the hope that my advisor sees the
advantages of using Emacs (instead of the proprietary word processors).
I'm a fan
Hello,
Kevin Zettler writes:
> Apologies if this is a duplicate. I first sent when I wasn't registered
> with the mailing list. Looks like org Gmane is down
> http://news.gmane.org/gmane.emacs.orgmode I get a 404.
>
> I suddenly am unable to open my org agenda. Invoking
Hello,
Tim Stewart writes:
> * lisp/org.el (org--get-expected-indentation): Fix indentation within
> lists after blocks that support a special editing environment.
>
> Testing shows that the indentation within lists is incorrect after
> `example-block', `export-block', and
Hello,
Yuri Lensky writes:
> I now understand what you mean by the second call to symbol-value not being
> needed. The previous behavior only chose this "branch" of the cond if
> symbol-value was not nil. To keep this behavior but only have one call to
> symbol-value, why not
16 matches
Mail list logo