I'm still slowly chewing on making more use of log items, and found a
small bug in org-log-beginning. It contains a partial re-implementation
of something we already have a function for: org-log-into-drawer. It was
causing me occasional bugs, but I only just looked into it.
I'm not sure the commit
When tangling a file whose source code blocks have capitalized BEGIN_SRC and
END_SRC (as produced by
> On Dec 13, 2014, at 5:07 PM, Nicolas Goaziou wrote:
> I don't think it needs to vary. As I suggested already, we can use cells
> contents (in the appropriate column) as trimmed strings. So, it could be
> built-in.
>
> Do you see any downside to it?
Well, I’m just going by what happens now. I
Jon Snader writes:
> The extraction function varies with the type of sort so it has to be
> specified one way or the other.
I don't think it needs to vary. As I suggested already, we can use cells
contents (in the appropriate column) as trimmed strings. So, it could be
built-in.
Do you see any
Hello,
Vasilij Schneidermann writes:
> I'm using the footnote facility in an org document expecting an exported
> Markdown document to provide hyperlinks between the reference and the
> footnote. Here's some sample Markdown text:
>
> Lots of text[fn:1]. Even more text
>
> [fn:1] Lies.
>
Hi Kevin,
> Org-mode version 6.33x
O-o-okay. The current stable version is 8.2 and the export framework
changed in v8. If possible, you should upgrade.
"kevin.lemorzadec" writes:
> I am trying to do a latex loop in org mode. When I use the latex syntax
> directly, the character "{" are expor
Hi,
Attached is a patch that enables footnotes in INCLUDEd documents when
using :lines and friends. It stores the footnotes in a hash-table
initialized in `org-export-expand-include-keyword' and updated via
`org-export--prepare-file-contents'. The footnotes are then inserted when
all include key
Hi,
I am trying to do a latex loop in org mode. When I use the latex syntax
directly, the character "{" are exported as"\{" as in case 1 below. If I
use ‘\(...\)’ it does keep the "{" characters but the ‘\(...\)' stays in
the .tex created (case 2 below) giving me an error when I try to generate
the
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
--
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
--
Hi Vikas,
2014ko abenudak 13an, Vikas Rawal-ek idatzi zuen:
>
> On 13-Dec-2014, at 3:42 pm, Daniele Pizzolli wrote:
>> Look at:
>> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html
>>
>> Use ESS to step through evaluation line-by-line
>>
>> Use C-c ' to visit the edit buffer fo
> On Dec 13, 2014, at 11:01 AM, Nicolas Goaziou wrote:
> `org-do-sort' is an internal function, which isn't meant to be used
> publicly. It really should be named `org-table--do-sort' and be moved
> within "org-table.el". OTOH, we can extend `org-table-sort-lines' to
> allow custom sorting funct
Hi Thierry
On Fri, Dec 12, 2014 at 10:04 PM, Thierry Banel wrote:
> Le 12/12/2014 18:15, Michael Brand a écrit :
> Seems doable.
> Would tie the spreadsheet and orgaggregate seamlessly.
> Very appealing!
>
> Are you willing to help me implement those steps?
Where necessary I try to help.
I woul
Nicolas Goaziou writes:
>> The new tests don't work on Emacs23, mainly due to the use of cl-letf.
>
> I fixed the `cl-letf' issue, thank you. Is there anything else to do?
Not with respect to this change, the tests are now all passing.
However, Emacs master seems to have changed the signature for
Hello,
Achim Gratz writes:
> The new tests don't work on Emacs23, mainly due to the use of cl-letf.
I fixed the `cl-letf' issue, thank you. Is there anything else to do?
Regards,
--
Nicolas Goaziou
Jon Snader writes:
> The problem with that solution is that the user has to answer the
> additional prompts every time he calls org-table-sort-lines with
> a custom sort. Imagine, for example, a networking researcher who often
> builds tables that he or she wants to sort by IP address (or any oth
> On Dec 13, 2014, at 9:29 AM, Nicolas Goaziou wrote:
> I think my proposal is simpler: add ?f and ?F to built-in options, in
> which case user is prompted for a custom sorting function (in your case,
> `org-ip-lessp'). It is also more consistent with `org-sort-list’.
The problem with that solu
Jon Snader writes:
> My idea for making it table driven is to add an alist whose elements look
> something like
>
> (prompt-char prompt extraction-function compare-function
> reverse-compare-function with-case-extraction-function)
>
> The alist would be initialized with the built-in options (in
Hello,
Toby Cubitt writes:
> Did this patch get lost in the noise?
Probably.
> It's a fairly straightforward one, which simply adds a useful new
> archiving function without touching much else.
>
> Archiving by date seems such an obvious omission from the existing
> archiving commands, I would
> On Dec 12, 2014, at 5:58 PM, Nicolas Goaziou wrote:
> However I think the feature implemented is too specific. Instead,
> `org-do-sort' could provide a way to pass an arbitrary predicate,
> like ?f and ?F in `org-sort-list'.
>
> WDYT?
Actually, when I originally looked at org-do-sort, my fir
Alan Schmitt writes:
> So you are correct the footnote applies to the text search. However, I
> think is also applies to the headline search (as suggested by the second
> line of the snippet). In other words, if I search for
>
> file:projects.org::*Headline
>
> with `org-link-search-must-match-
Daniel Clemente writes:
> No need to teach the user the differences of a :CLOCK: vs
> a :PROPERTIES: or drawer vs. metadata.
The difference is important, e.g., wrt export.
> Users who type can do a simpler distinction:
> 1. things you type yourself
> 2. things that appear/change/disappe
El Sat, 13 Dec 2014 12:33:16 +0100 Nicolas Goaziou va escriure:
> > But these are technical details, not relevant to a non-programmer.
>
> Which basically means nothing, because everything ultimately boils down
> to technical details.
>
That's always true. But UIs still need to be simple.
On 13-Dec-2014, at 3:42 pm, Daniele Pizzolli wrote:
> Look at:
> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html
>
> Use ESS to step through evaluation line-by-line
>
>Use C-c ' to visit the edit buffer for your code block
>Use ess-eval-line-and-step to evaluate each
Nicolas et al,
I'm sure the choice for \emsp was a valid one. \emsp is not the bug, it
triggers a bug in the alignment routine which screws up somehow. If
alignment takes place after displaying the blanks, things turn out OK. I
tried to install a custom formatter (Cutomizable: Org Clock Clocktable
Hello,
On 2014-12-12 18:29, Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> I think the footnote in
>> http://orgmode.org/manual/External-links.html#fn-1 is in the wrong
>> place, it should be on the next line.
>>
>> Here is a patch to fix it. If you prefer I can push it directly
On 2014-12-12 12:01, Kyle Meyer writes:
> Alan Schmitt wrote:
>> My agenda is fairly big, and it takes a few minutes to generate it.
>
> Wow.
I meant seconds (about 20 seconds). But is feels like minutes ;)
>> When I need to refile many items to different places (so bulk edit is
>> not an opti
Daniel Clemente writes:
> But these are technical details, not relevant to a non-programmer.
Which basically means nothing, because everything ultimately boils down
to technical details.
> What a new user sees with the default settings as of today is:
Aren't you confusing your expectations a
El Fri, 12 Dec 2014 19:25:25 +0100 Nicolas Goaziou va escriure:
>
> > Of course everything's text, but if there's no distinction between
> > drawers/headers and text, that's the problem. Those headers are metadata
> > written and managed by org and must follow some rules,
>
> This is incorrect.
Hello,
Vikas Rawal writes:
> I have an R source code blocks called with the ":results value”
> option. I evaluate the code with C-c. When I do that, in my R session
> buffer, I get to see several + + + until the final value is obtained,
> and then the final value is shown, and inserted in my Org
No problem, I've gone ahead and packaged my changes here:
https://github.com/calvinwyoung/org-autolist
I'll also submit this to melpa to make it easier to install.
I'd love hear how other Org'ers on this list feel about it. If folks find
it useful, I'd be happy to publish it on Worg as well.
Best
Nicolas Goaziou writes:
> Applied (with a minor change in `org-timer--get-timer-title'). Thank you.
The new tests don't work on Emacs23, mainly due to the use of cl-letf.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & addit
33 matches
Mail list logo
