Hi!
Le 17/01/2015 04:48, Aaron Ecay a écrit :
Hi Thierry,
2014ko abenudak 22an, abonnements-ek idatzi zuen:
Is this better?
I’m very sorry, I lost track of your email over the winter holidays and
am only now coming back to it. What’s more, you sent the latest patch
only to me and not the org
Hi Thierry,
2014ko abenudak 22an, abonnements-ek idatzi zuen:
>
> Is this better?
I’m very sorry, I lost track of your email over the winter holidays and
am only now coming back to it. What’s more, you sent the latest patch
only to me and not the org list, so no one else was keeping an eye on i
Hi Chuck,
Thanks for the patches.
I agree with Nicolas about the issue of multi-line results for inline
blocks. I think he already raised any comments I would have made about
the code. Additional comments about broader issues:
2015ko urtarrilak 12an, "Charles C. Berry"-ek idatzi zuen:
> (defu
i think i found one of the bugs in org.el's org-show-context. is
anybody willing to confirm and fix it?
On 8/5/13, Samuel Wales wrote:
> ;; bug 1: when point is in entry text, the first child of that
> ;; entry shows, but its siblings (i.e. the other children) do
> ;; not show, even though
Hi Dieter,
Dieter Van Eessen writes:
> Hello Rasmus,
>
> Thank you for the fast reply, the link you've given on interpreting is very
> useful ! Also didn't know there existed such thing as the org-dp library to
> manipulate org-elements, I'll sure check it out.
I don't know org-dp myself, but T
"Thomas S. Dye" writes:
> Thierry Banel writes:
>
>> You are not missing anything. MD or ORG do the job. It is just that your
>> public is made of Emacs users, and Org-mode users. So ORG sounds
>> familiar. GitHub renders pretty well ORG documents. And maybe someday
>> there will be converters f
Hi Johan,
Thanks for raising this issue.
2014ko abenudak 10an, "Johan W. Klüwer"-ek idatzi zuen:
>
> I encountered a problem with unmatched double quotes in an org-babel
> table of results. Seems like the issue lies with escaped double quotes:
>
> (org-babel-script-escape "[[\"a\", \"b\\\"\"]
"Charles C. Berry" writes:
> I've attached three patches and two files that show the behavior under
> the current master (12 Jan 2015,
> e0879b03d08bb4acc663084076370482f61e8698) and under the patched
> version.
Thank you. Some comments follow.
> With the patches, inline source block results ca
The alternative is to supply a minimum reproducible recipe starting with
emacs -Q, then someone else can debug it.
BTW, it's a nice gesture to provide screencasts, but I don't think
anyone developing Emacs finds them particularly useful for debugging, so
no need to keep providing those AFAICS.
Hello,
Dieter Van Eessen writes:
> The reason I've tried this (and the internal org-element--parse-elements)
> is because I'd prefer not having to parse the whole buffer and still get
> the contents. The local parsing functions (org-element-at-point) and
> (org-element-context) don't contain con
Noah Slater apache.org> writes:
> I'm moving point over a habit in the agenda, clocking on with I,
> switching buffer a few times, then switching back and hitting O.
> Occasionally, I get a "Clock start time is gone" message. I just got
> one now. If I go to the node, I see this:
>
> :LOGBOOK:
>
Hello Rasmus,
Thank you for the fast reply, the link you've given on interpreting is very
useful ! Also didn't know there existed such thing as the org-dp library to
manipulate org-elements, I'll sure check it out.
More about question number 3:
>> 3) How can the output of (org-element-parse-secon
Michael Ziems writes:
> thanks for the reply. is this information already helpful:
>
> - command-execute 1331 92%
> - call-interactively 1327 91%
> - org-shiftdown 302 20%
>- call-interactively 302 20%
> - org-priority-down 302 20%
>org-priority 302 20%
> - org-shiftup
Hello,
thanks for the reply. is this information already helpful:
- command-execute 1331 92%
- call-interactively 1327 91%
- org-shiftdown 302 20%
- call-interactively 302 20%
- org-priority-down 302 20%
org-priority 302 20%
- org-shiftup 293 20%
- call-interactivel
Hello,
seth andrews writes:
> C++ (or c code for that matter) that needs to link to any libraries will
> not compile with babel. In the function org-babel-C-execute, the file name
> is given last, making it impossible to pass compiler flags that will effect
> linking. A simple fix is to switch
Hello,
Michael Ziems writes:
> i got two windows machines: one is a surface with an i5 cpu and
> a desktop machine with an amd 6 core cpu.
>
> on both machines i have org mode 8.2.10.
>
> when i switch the prioity in an 15k line org file having 614kbyte in
> size on the i5 machine the system is
Hello,
i got two windows machines: one is a surface with an i5 cpu and a
desktop machine with an amd 6 core cpu.
on both machines i have org mode 8.2.10.
when i switch the prioity in an 15k line org file having 614kbyte in
size on the i5 machine the system is really laggy and it takes up to
Thierry Banel writes:
> You are not missing anything. MD or ORG do the job. It is just that your
> public is made of Emacs users, and Org-mode users. So ORG sounds
> familiar. GitHub renders pretty well ORG documents. And maybe someday
> there will be converters from ORG to INFO.
Does INFO refer
> From: Fabrice Niessen
> Cc: dgu...@yandex.ru, 19...@debbugs.gnu.org
> Date: Fri, 16 Jan 2015 19:31:38 +0100
>
> > Looks like an infloop due to display or overlay strings with text
> > properties. Can you reproduce this in an unoptimized build?
>
> Sure, if you can point me to such a version
Fabrice Niessen writes:
> On Cygwin (I'm on Windows), that does not seem to work:
>
> kill -10
> kill -USR2
Cygwin kill only works with Cygwin processes, while your backtrace is
from a Windows Emacs. The problem of the incomplete traces might also
be related to your attempt to attach a Cygw
Hi Dieter,
Nicolas will probably reply at some point and he has much greater (∞ more)
insight in this topics. None the less, I hope the below message will
help a bit.
Dieter Van Eessen writes:
> 1) How to use org-element-content? Returns nil when used on elements parsed
> by org-element--parse
Le 15/01/2015 23:41, Phillip Lord a écrit :
> Thierry Banel writes:
>
>> Le 15/01/2015 17:11, Phillip Lord a écrit :
>> One possibility, not as good as info, but quite easy, is given by
>> GitHub. Replace your current README.md with a README.org, in org-mode
>> syntax.
> Why this replacement? md o
Hello,
New to the list. Got some questions regarding the use of the org-element
api. I've already learned alot by reading the emacs help and org-developers
section. and the online org-element-docstrings have been very helpful. I'm
not a highly skilled lisp-programmer, but got good grip on the basi
Eli Zaretskii wrote:>> From: Fabrice Niessen
>> Cc: dgu...@yandex.ru, 19...@debbugs.gnu.org
>> Date: Fri, 16 Jan 2015 13:04:00 +0100
>>
>> (gdb) thread 1
>> [Switching to thread 1 (Thread 17252.0x44f0)]
>> #0 0x01142191 in Fnext_single_property_change (position=position@entry=540,
>> prop=6
Hi Sebastien,
2015ko urtarrilak 16an, Sebastien Vauban-ek idatzi zuen:
>
> Hello,
>
> When ~code~ is converted to LaTeX, it becomes \verb~code~; i.e., it uses
> a potentially "dangerous" character, in this case `~' which is active.
>
> In most cases, it is unnoticeable, but in some environments
Sebastien Vauban
writes:
> Hello,
>
> When ~code~ is converted to LaTeX, it becomes \verb~code~; i.e., it uses
> a potentially "dangerous" character, in this case `~' which is active.
>
> In most cases, it is unnoticeable, but in some environments, it breaks.
>
> The solution is to protect the co
> From: Fabrice Niessen
> Cc: dgu...@yandex.ru, 19...@debbugs.gnu.org
> Date: Fri, 16 Jan 2015 13:04:00 +0100
>
> (gdb) thread 1
> [Switching to thread 1 (Thread 17252.0x44f0)]
> #0 0x01142191 in Fnext_single_property_change (position=position@entry=540,
> prop=62947906, object=118795585, l
Hello,
When ~code~ is converted to LaTeX, it becomes \verb~code~; i.e., it uses
a potentially "dangerous" character, in this case `~' which is active.
In most cases, it is unnoticeable, but in some environments, it breaks.
The solution is to protect the command, what the attached patch does.
PS
>
> >> >> Another option would be to have another option to indent only planning
> >> >> info, properties drawer, and every drawer located right after it, à la
> >> >> `org-log-state-notes-insert-after-drawers'. At least, it couldn't break
> >> >> structure.
> >
> > Is this possible?
>
> Why wo
Eli Zaretskii wrote:
>> From: Fabrice Niessen
>> Cc: 19...@debbugs.gnu.org
>> Date: Fri, 16 Jan 2015 12:27:16 +0100
>>
>> OK, so I just reproduced the problem once again, then:
>>
>> - tried to C-g in Emacs: impossible!
>> - launched GDB
>> - source ~/.gdbinit
>> - thread 1
>> - thread apply all
Eli Zaretskii wrote:
>> From: Fabrice Niessen
>> Cc: 19...@debbugs.gnu.org
>> Date: Fri, 16 Jan 2015 12:16:26 +0100
>>
>> Eli Zaretskii wrote:
From: Glenn Morris
Cc: Fabrice Niessen , 19...@debbugs.gnu.org
Date: Thu, 15 Jan 2015 16:37:36 -0500
I just want to note that
> From: Fabrice Niessen
> Cc: 19...@debbugs.gnu.org
> Date: Fri, 16 Jan 2015 12:27:16 +0100
>
> OK, so I just reproduced the problem once again, then:
>
> - tried to C-g in Emacs: impossible!
> - launched GDB
> - source ~/.gdbinit
> - thread 1
> - thread apply all backtrace
>
> Still, the backt
> From: Fabrice Niessen
> Cc: 19...@debbugs.gnu.org
> Date: Fri, 16 Jan 2015 12:16:26 +0100
>
> Eli Zaretskii wrote:
> >> From: Glenn Morris
> >> Cc: Fabrice Niessen , 19...@debbugs.gnu.org
> >> Date: Thu, 15 Jan 2015 16:37:36 -0500
> >>
> >>
> >> I just want to note that there seems to be a
Eric Abrahamsen wrote:
> Fabrice Niessen writes:
>> Eli Zaretskii wrote:
From: Glenn Morris
Cc: Fabrice Niessen , 19...@debbugs.gnu.org
Date: Thu, 15 Jan 2015 16:37:36 -0500
I just want to note that there seems to be a tendency to try and
use gdb to debug Org proble
Fabrice Niessen wrote:
> OK, so I just reproduced the problem once again, then:
>
> - tried to C-g in Emacs: impossible!
> - launched GDB
> - source ~/.gdbinit
> - thread 1
> - thread apply all backtrace
>
> Still, the backtrace is not as long as normal, and I don't get any GDB
> prompt anymore!
>
Eli Zaretskii wrote:
>> Date: Fri, 16 Jan 2015 00:06:58 +0300
>> From: Dmitry Gutov
>> CC: 19...@debbugs.gnu.org
>>
>> On 01/15/2015 09:14 PM, Eli Zaretskii wrote:
>>
>>> But you didn't even show the backtrace from the main (a.k.a. "Lisp")
>>> thread. Your backtrace is from thread 15, whereas t
Fabrice Niessen
writes:
> Eli Zaretskii wrote:
>>> From: Glenn Morris
>>> Cc: Fabrice Niessen ,
>>> 19606-ubl+/3LiMTaZdePnXv/o...@public.gmane.org
>>> Date: Thu, 15 Jan 2015 16:37:36 -0500
>>>
>>>
>>> I just want to note that there seems to be a tendency to try and use
>>> gdb to debug Org p
Eli Zaretskii wrote:
>> From: Glenn Morris
>> Cc: Fabrice Niessen , 19...@debbugs.gnu.org
>> Date: Thu, 15 Jan 2015 16:37:36 -0500
>>
>>
>> I just want to note that there seems to be a tendency to try and use
>> gdb to debug Org problems, when debug-on-quit and ctrl-g might work.
>
> Very true.
Alan Schmitt writes:
> I gave this a try and it works well.
>
>> Can I ask, why do you want to kill the buffer? Why not just bury it?
>
> Because otherwise I get this the next time I start lentic for the same
> file:
>
> A buffer is visiting /Users/schmitta/tmp/lentic_test.org; proceed? (y or n)
Hello,
Calvin Young writes:
> If my cursor is in a description list item, what's the recommended way of
> getting the point at the beginning of the description list text (i.e.,
> after the bullet character)? To illustrate, given the following description
> list item, I'd like to get the point re
Nicolas Richard writes:
> Calvin Young writes:
>> How do I need to massage this to give me the beginning of the whole
>> list item? Is there a recommended solution that'd work for both
>> description lists *and* plain lists?
>
> This seems to work for me:
>
> (defun yf/org-beginning-of-item ()
>
On 2015-01-15 22:28, phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
> So, local variables comes *after* the ends here line. Currently, the
> "ends here" line needs to be *inside* a source block, so you would have...
>
> ;; #+begin_src emacs-lisp
> (message "foo")
> ;; #+end_src
>
> ;; #+begin
Hello,
Myles English writes:
> Yes, I can see similar behaviour for clocked tasks. That is to say, with
> this file contents:
>
> #+COLUMNS: %40ITEM(Task) %17Effort(Estimated Effort){:} %CLOCKSUM
> * TODO Earn money
> :PROPERTIES:
> :Effort: 0:10
> :END:
>
> * TODO Drink tea
Alan Schmitt writes:
> Would the following work as a regexp builder that allows arbitrary space
> and cookies between each word (making sure there is at least one)?
>
> #+begin_src emacs-lisp
> (defun org-heading-regexp-build (s)
> (let* ((sp (reverse (org-split-string s)))
You can ignore SP f
Nicolas Petton writes:
> Here's a new version that uses :RSS_TITLE. Do you think it's good enough
> for a first patch?
Thanks. It would be nice to document the feature somewhere in the
library.
> +(title (or (org-element-property :EXPORT_TITLE headline)
I think you sent the wrong patch
> [[mailto:sub...@bugs.debian.org?subject=%20My%20problem%20with%20hkl...&body=Package:%20hkl%0AVersion:%20@VERSION@%0A%0AI%20found%20this%20problem%20in%20hkl...]]
Thanks a lot this is exactly what I wanted :).
Thanks also to the other's for the time they spent answering my question.
Cheers
Fr
> From: Glenn Morris
> Cc: Fabrice Niessen , 19...@debbugs.gnu.org
> Date: Thu, 15 Jan 2015 16:37:36 -0500
>
>
> I just want to note that there seems to be a tendency to try and use gdb
> to debug Org problems, when debug-on-quit and ctrl-g might work.
Very true.
> Date: Fri, 16 Jan 2015 00:06:58 +0300
> From: Dmitry Gutov
> CC: 19...@debbugs.gnu.org
>
> On 01/15/2015 09:14 PM, Eli Zaretskii wrote:
>
> > But you didn't even show the backtrace from the main (a.k.a. "Lisp")
> > thread. Your backtrace is from thread 15, whereas the main thread is
> > threa
Hi,
This works fine for me with mu4e as the mail client. It's not guaranteed
to work with every client, but it can be a solution for personal
use. It's not necessarily the best solution.
The general syntax is mailto:address?subject=text&body=text
Some applications even allow adding attachments
Yuri Niyazov writes:
> I'd like to hire a programmer to hack on some things in org-mode for
> my use. If these improvements are contributed back the main org-mode
> repository, would the copyright assignment have to come from me, or
> from the programmer?
It depends on who owns the copyright. If
50 matches
Mail list logo
