Hi Bastien,
I've attached a patch for ox-extra which doesn't yet include the
option for choosing specific tag names (the 'ignore' tag is currently
hard-coded). Feel free to modify / commit it.
Regards,
Mark
On Tue, Jul 29, 2014 at 10:31 AM, Bastien wrote:
> Hi Nicolas,
>
> Nicolas Goaziou w
Gour wrote:
> Excuse me for dumb question, but is this package meant to be something
> like org-contacts NG (something which we would really like to have)?
i don't think that's a dumb question at all!
My original motivation for developing org-vcard was to create part of a
pipeline for synchroni
when i do capture, i expect it to work the same in any buffer. but
editing source code makes it ask me for a code line label. this is a
great feature, but it breaks my flow when it asks me so i want to turn
that feature off. what is the variable to turn it off? i want
capture to work the same
to reproduce in maint:
c-c ' on a fairly large shell source block
move point someplace
c-x c-s
sometimes point moves
sometimes the position in the window recenters
it seems quite random
what i expected was no changes of anything
thanks
Hi Nathaniel
On Tue, Jul 29, 2014 at 2:03 PM, Nathaniel Flath wrote:
> This patch speeds up org-table-recalculate by removing all 'message'
> function calls. Additionally adds an early check for whether there are any
> formulas and only executes the rest of the function if so.
As far as I under
On Wed, Jul 30, 2014 at 2:52 AM, Eric Abrahamsen
wrote:
> The vcount function will count the number of elements in a vector, so
> you could probably pass a range reference, like @1..@> (first row to
> last row) to vcount.
Yes.
> I think empty rows would be omitted, though.
It depends on whether
Hello, recently I tried to install the latest development snapshot from Git
through the following procedure, which has worked for me perfectly until
now:
- make cleanall
- make up0
- make install
When the build system gets to creating the documentation (just the info
file) these error lines appea
Is there any way to easily turn of CLOCK blocking?
Currently it appears the otherwise-valid inactive timestamp entries in a CLOCK
line
are treated as invisible when creating agenda views, viewing in agendas, etc
using v [
Example:
* TEST HEADLINE WORKING HERE
:TIMELOGS:
CLOCK: [2014-08-01 Fri
Nicolas Goaziou writes:
> Hello,
>
> It's not. Thanks for the patch. Some comments follow.
>
Hi, tried to fix those issues.
>From 82cb7209c912798b43a91b3dde1dd4428e09580e Mon Sep 17 00:00:00 2001
From: Moritz Kiefer
Date: Thu, 31 Jul 2014 17:45:36 +0200
Subject: [PATCH] ox-latex.el: Add page n
SabreWolfy writes:
>> I released Org 8.2.7c.
>
> Should this be available via ELPA[1]?
It is.
--
Bastien
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.
At Fri, 01 Aug 2014 01:21:47 +0200,
Thorsten Jolitz wrote:
>
> Hi List,
>
> here is my first take of rewriting `org-entry-properties'.
>
> The existing function predates the new parser and some Org variables,
> and thus does the parsing and the property classification itself. The
> new version l
Hello,
SabreWolfy writes:
> Bastien gnu.org> writes:
>
>> I released Org 8.2.7c.
>
> Can someone point me to the changelog for this? Is not here[1]. Is it on
> that git thing somewhere? :)
>
> [1] http://orgmode.org/Changes.html
8.2.* releases are bugfixes releases. The changelog is the same a
John Lusk writes:
> You probably already know about this problem, but here's a thousand
> words:
That has nothing to do with Org. Your font (or any of the fallback
fonts that are tried instead) doesn't provide a single-width glyph for
the unicode codepoint you're using. Emacs usually gets this r
Yeah, constant-width font. I tried switching to utf-16, but that didn't
help.
On Fri, Aug 1, 2014 at 12:11 PM, Grant Rettke
wrote:
> Layout works for ASCII width characters
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2009-02/msg00323.html
>
> The maintainers surely may tell you more,
Bastien gnu.org> writes:
> I released Org 8.2.7c.
Should this be available via ELPA[1]?
[1] http://orgmode.org/elpa.html
> > The org-plus-contrib package on http://orgmode.org/elpa/ should provide
> > org-8.0
> Why do you think it does not?
To be frank, I'm not sure how packages declare what they provide.
org-plus-contrib has this
(define-package "org-plus-contrib" "20140526" "Outline-based notes management
and o
Bastien gnu.org> writes:
> I released Org 8.2.7c.
Can someone point me to the changelog for this? Is not here[1]. Is it on
that git thing somewhere? :)
[1] http://orgmode.org/Changes.html
John Lusk writes:
> Hey, org-mode crew. Awesome app; I love it. It's pretty much the
> only thing that keeps me in emacs these days (apart from writing
> Python code :) ).
>
> You probably already know about this problem, but here's a thousand
> words:
>
>
> [cid]
I have a bunch of dot settings that I want to set globally. I hacked it like
this:
(setq va/org-dot-preamble "digraph g {
rankdir=LR nodesep=0.2 ranksep=0.1 arrowsize=0.2
node [fontname=courier fontsize=10 margin=\"0.02,0.01\" shape=box width=0.1
height=0.1]
edge [fontname=courier fontsize
Layout works for ASCII width characters
https://lists.gnu.org/archive/html/emacs-orgmode/2009-02/msg00323.html
The maintainers surely may tell you more, though.
Grant Rettke | ACM, ASA, FSF, IEEE, SIAM
g...@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrat
Hey, org-mode crew. Awesome app; I love it. It's pretty much the only
thing that keeps me in emacs these days (apart from writing Python code :)
).
You probably already know about this problem, but here's a thousand words:
(I hope that comes through.)
I'm sorry I only have time to whine and
Hello,
Thorsten Jolitz writes:
> here is my first take of rewriting `org-entry-properties'.
Interesting. A first round of comments follows.
> Implementation goals were:
>
> 1. (almost) full backward-compability. The parser upcases user
>properties, thus case-sensitivity is lost after pars
Bastien writes:
Hi Bastien,
> Thorsten Jolitz writes:
>
>> here is my first take of rewriting `org-entry-properties'.
>
> I didn't take the time to closely look at the change, but thanks
> for working on this.
>
> My main concern with anything that touches `org-entry-properties'
> is whether ag
Nicolas Goaziou wrote:
> Hello,
>
> Nicolas Berthier writes:
>
>> In any case, as advised earlier in the discussion, I updated one patch
>> to integrate new tests for the new feature. I also slightly simplified
>> the HTML export patch to avoid useless display attributes.
>
> Thank you for this n
Hi Nicolas,
Nicolas Goaziou writes:
> A better place would be the line below planning info, if any, or below
> the headline otherwise.
Yes, exactly.
--
Bastien
Hi Charles,
Charles Berry writes:
> The docstring for `org-preview-latex-fragment' still says:
>
> "The images can be removed again with \\[org-ctrl-c-ctrl-c]."
>
> Maybe change that to "\\[org-preview-latex-fragment]"?
Fixed, thanks. `org-preview-latex-fragment' is now named
`org-toggle-latex
Hi Thorsten,
Thorsten Jolitz writes:
> here is my first take of rewriting `org-entry-properties'.
I didn't take the time to closely look at the change, but thanks
for working on this.
My main concern with anything that touches `org-entry-properties'
is whether agenda generation is affected in
Hello,
Moritz Kiefer writes:
> This is my first attempt at elisp so it's probably terrible code
It's not. Thanks for the patch. Some comments follow.
> * lisp/ox-latex.el (org-latex--inline-image): Use page
> number (:search-option) of pdf links as page option in includegraphics
Missing full
Hello,
Andrea Rossetti writes:
> When I:
>
> - create a "BEGIN_SRC org" block (let's call it "the external
> BEGIN_SRC")
> - hit C-c ' to edit its contents
> - create two consecutive, non-nested "BEGIN_SRC org" blocks
> (let's call them "the internal BEGIN_SRCs")
> - hit C-c ' to
> I didn't read the other thread is details, but it seems the most
> sensible thing to do is alter the org fill function(s). These seems
> to rely on org-element, though, and I'm guessing that is why a syntax
> change is necessary, yes?
I would be perfectly happy with this behavior. Can't comment
Hi Bastien,
> This is the fault of Org.
>
> I fixed this in master by removing `org-block-background'.
>
> This is radical but I think this is really better:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=f8b42e8
>
> Sebastien, let's think about another way of getting a
> color for the back
Andy Moreton gmail.com> writes:
> > I tried like that:
> > emacsclient --eval '(org-search-view nil "search string")'
> > but with no success.
> > In the command line I get the error message:
> > *ERROR*: End of file during parsing
>
> cmd.exe has strange quoting rules. Does this work for you ?
>
33 matches
Mail list logo