Hi, everyone,
Start from Org-mode 8, the plain text export is fixed width with line
break and it is very unconvenient to show in the text edit like libreoffice and
so on.
I also try (setq org-ascii-text-width 10) in my .emacs but the title
and the author align to the middle in 100
Titus von der Malsburg writes:
> While that may be a valid solution for some people, it is
> certainly not the Emacs way of doing things.
That's right. It is the Org mode way of doing things in Emacs.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Then it might be a version issue. I'm looking at Org-mode version
8.3beta (release_8.3beta--gf8d1d3 @
/Users/dk/.emacs.d/src/org-mode/lisp/).
What version are you using?
All the best,
Tom
Lawrence Bottorff writes:
> Sorry, not seeing any
>
> prop: Toggle inclusion of property drawers, or
Sorry, not seeing any
prop: Toggle inclusion of property drawers, or list properties to include
(‘org-export-with-properties’).
in 12.3 (online manual). Tried
#+OPTIONS: prop:t
in my buffer and it didn't work either.
On Sun, May 17, 2015 at 7:08 PM, Thomas S. Dye wrote:
> Lawrence Bottorff
On 2015-05-17 Sun 14:15, Rasmus wrote:
> Hi Jarmo,
>
> Jarmo Hurri writes:
>
>> Rasmus writes:
>
>>> With your behavior you can (i) break the TODO tag; (ii) break the cookie;
>>> (iii) break the tag. At least (i) and (ii) are quite destructive.
>>
>> I am not sure what you mean, since a single
Lawrence Bottorff writes:
> Sorry, but I can't find any reference to org-export-with-properties . Where
> might it be mentioned?
See 12.3 Export settings,
,
| ‘prop:’ Toggle inclusion of property drawers, or lis
Sorry, but I can't find any reference to org-export-with-properties . Where
might it be mentioned?
On Sun, May 17, 2015 at 5:51 PM, Nicolas Goaziou
wrote:
> Hello,
>
> Lawrence Bottorff writes:
>
> > Okay, after sifting through the reference I did see something about how
> > properties can neve
Rasmus writes:
> FWIW, I did not like the syntax Nicolas suggested in that thread. It
> reminded me too much of *XML (which is also true with inlinetasks
> BTW).
Well, that's sad. It brings interesting features you cannot have with
link-like syntax.
Regards,
Rasmus writes:
>> You shouldn't use `org-next-visible-heading' as statistics cookie
>> updates shouldn't depend on current visibility.
>
> That's why I used org-with-wide-buffer.
This is orthogonal. `o-w-w-b' is about narrowing. `o-n-v-h' ignores
inlinetasks.
> But perhaps a better solution wou
Hello,
Lawrence Bottorff writes:
> Okay, after sifting through the reference I did see something about how
> properties can never be exported;
See `org-export-with-properties'.
Regards,
--
Nicolas Goaziou
Hi Jarmo,
Jarmo Hurri writes:
> Rasmus writes:
>> With your behavior you can (i) break the TODO tag; (ii) break the cookie;
>> (iii) break the tag. At least (i) and (ii) are quite destructive.
>
> I am not sure what you mean, since a single undo will always heal the
> line again, regardless o
Okay, after sifting through the reference I did see something about how
properties can never be exported; however, drawers can be (general)
exported -- unless you tell org-mode to hide them. But drawers don't allow
any key:value sub-categories like properties do, right? Any way for me to
have my ca
Rasmus writes:
Greetings Rasmus.
>> I would suggest that the original interpretation of Enter would not
>> be messed with. Messing with Alt-Enter and such is fine, but Enter,
>> please no.
>
> I disagree. Consider the more complete example:
>
> * TODO [#A] foo bar:tag:
>
> With your be
Eric S Fraga writes:
> I'm not sure I understand what is misleading about the above? The note
> is indeed intended to belong to the first item on the list.
The misleading part, IMO, is that it is not obvious whether the
inlinetasks belong to the list item or not. Normally something that
belong
On Sunday, 17 May 2015 at 20:51, Nicolas Goaziou wrote:
[...]
> Anyway, we could fix it in another way. Eric's example,
>
> - [ ] the first task
>
> *** This is something to note
> *** END
>
> - [ ] another list of tasks
>
> is misleading because it's really t
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Consider this example:
>>
>> |---+---+---|
>> | a | b | c |
>> | d | e | f |
>> |---+---+---|
>> | 1 | 2 | 3 |
>> | 4 | 5 | 6 |
>> |---+---+---|
>> | 5 | 7 | 9 |
>> #+TBLFM: @5=vsum(@II..@III)
>>
>> Insert a hline after |a|b|c|. The formul
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Can you try the attached patch? It seems to work on my system, but
>> probably more cleanup should be made wrt the "old" outline-functions.
>> + (org-with-wide-buffer
>> + (org-next-visible-headi
Hello,
Rasmus writes:
> Consider this example:
>
> |---+---+---|
> | a | b | c |
> | d | e | f |
> |---+---+---|
> | 1 | 2 | 3 |
> | 4 | 5 | 6 |
> |---+---+---|
> | 5 | 7 | 9 |
> #+TBLFM: @5=vsum(@II..@III)
>
> Insert a hline after |a|b|c|. The formula is now broken.
What should happen to the f
Titus von der Malsburg writes:
> You mean I can specify a path by typing it in when prompted by
> `org-refile'? Because the documentation of `org-refile-targets' doesn’t
> mention the possibility to specify paths as far as I can see.
See `org-refile-use-outline-path'.
Regards,
Hello,
Rasmus writes:
> Can you try the attached patch? It seems to work on my system, but
> probably more cleanup should be made wrt the "old" outline-functions.
> + (org-with-wide-buffer
> +(org-next-visible-heading 1)
> +(
Hi All,
I recently had two "perspectives" published on using org-mode to write
scientific papers, and on reusing the data that is embedded in them! One
was published in an American Chemical Society journal:
http://kitchingroup.cheme.cmu.edu/blog/2015/05/17/New-publication-in-ACS-Catalysis-on-data
"eems" --> "seems"
(must learn to read my emails before I C-c C-c... ;-)
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1147-g0e5069
On Sunday, 17 May 2015 at 15:51, Rasmus wrote:
> Hi Eric,
[...]
> Can you try the attached patch? It seems to work on my system, but
> probably more cleanup should be made wrt the "old" outline-functions.
Hi Rasmus,
your patch eems to work just fine. I haven't done exhaustive testing
but no e
I want to display all my :PROPERTIES: drawers in a Latex/HTML export.
Couldn't find anything in the documentation to toggle the default hide
behavior off. Anyone know how to do this?
LB
On 2015-05-17 Sun 01:13, Nicolas Goaziou wrote:
> Capture and Refile are two very different concepts. In the former, you
> define a static, or a set of static, accurate location that may not
> exist yet. In the latter, you pile up existing locations that you filter
> interactively, depending on th
Hello,
Anders Johansson writes:
> I had an inlinetask that started with a link, like this:
>
> Inlinetask heading
> [[file:filename][link desc]] some text. Some more text.
> END
>
> It didn't fold on TAB. Looking into org-inlinetask-toggle-visibility I see
>
> ;
Hi,
I had an inlinetask that started with a link, like this:
Inlinetask heading
[[file:filename][link desc]] some text. Some more text.
END
It didn't fold on TAB. Looking into org-inlinetask-toggle-visibility I see
;; Inlinetask was folded: expand it.
((ge
Hi Eric,
Eric S Fraga writes:
> I often use checkbox lists for particular tasks. If any of the list
> items has an inline task (whether a task or not), the updating of the
> [/] cookie in the headline does not work. Attached is an example.
>
> Backtrace is also attached.
Thanks.
Can you try
Eric S Fraga writes:
> Mind you, having played around with emacs -Q and my test file, I have
> run into another bug. If I specify org-indent in the startup options, I
> get a very strange indentation. See attached screenshot. I wonder if
> this is related to my problem?
Probably 'cause you ha
Titus von der Malsburg writes:
> One minor cosmetic issue:
>
> * TODO foo bar :test:
>
> When I RET between foo and bar, the tag moves to the left. I think it
> would be nicer if it would stay where it was.
In the attached patch current colu
Mind you, having played around with emacs -Q and my test file, I have
run into another bug. If I specify org-indent in the startup options, I
get a very strange indentation. See attached screenshot. I wonder if
this is related to my problem?
Thanks,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs
Nicolas Goaziou writes:
> Also, shouldn't the final (delete-indentation ARG) be in the "else" part
> of the `if'?
It was, at least on my disk. I did not check the patch.
>> +(ert-deftest test-org-delete-indentation ()
>> + "Test M-^ (`org-delete-indentation') specification."
>
> I suggest to
When positioned at the end of an outline node, blocks will spill their
background color (defined by the `org-block-end-line' face) when the
node is folded.
To see this, paste the following lines into an Org buffer, and make
sure that a background color is set for `org-block-end-line':
* One
#+B
Please ignore my bug report for the moment. org works if I don't invoke
any of my customisations. I have obviously set something that makes the
updating of the cookie fail. Not sure what, mind you... Any suggestions
welcome, of course.
Sorry for the noise.
--
: Eric S Fraga (0xFFFCF67D), Emac
> On 16 May 2015, at 15:31, Lawrence Bottorff wrote:
>
> No worries. I can wait. Thanks again for your efforts.
I had some spare time today that I didn’t expect. I believe I have fixed the
bug.
Kind regards,
Bjarte
Hello,
I often use checkbox lists for particular tasks. If any of the list
items has an inline task (whether a task or not), the updating of the
[/] cookie in the headline does not work. Attached is an example.
Backtrace is also attached.
Thanks,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 25
Hi,
Vaidheeswaran C writes:
> (My future assignment is through, so the route is clear.)
Can you clarify on this? My understanding was that it was retracted a
while back under much fuss.
> I hope the above arrangement for merging my changes is agreeable to
> the maintainers. (Let me know what
Dear all,
I have not been able to be active as a maintainer since more than
half a year now.
I have been reading the mailing list, though, and Nicolas daily
commitment has been key in me being relaxed about tons of issues,
if not about the lack of a maintainer itself. I have only dealt
with priv
On Sunday 17 May 2015 01:48 PM, Nicolas Goaziou wrote:
>> How about making (1) a configurable option -- disabled by default --
>> > and moving it to trunk?
> I don't want syntax to be configurable.
Ok.
>> > I believe the answer depends MORE on how "stable" you think the new
>> > citation syntax
>> + (let ((string (concat " " (prog2 (and ARG (forward-line 1))
>> +(org-trim (delete-and-extract-region
>> (line-beginning-position)
>> +
>> (line-end-position)))
Also,
(concat " "
Hello,
Rasmus writes:
> Due to recent controversy about Org being lacking Microsoftesque detail I
> finally implemented org-delete-indentation, which is a function I have
> been missing forever.
Thank you.
> +(defun org-delete-indentation (&optional ARG)
> + "Join this line to previous and fi
Hello,
Christopher League writes:
> * org-notmuch.el (org-notmuch-search-open): Bug fix
> When opening a notmuch-search link, we use =message= to display the
> path at the bottom of the screen. This would signal "Not enough
> arguments for format string" when the path contained %-signs, as it i
Erik Hetzner writes:
> * lisp/org-attach.el (org-attach-commit): Check for .git/annex dir in
> addition to annex dir in root git dir to ensure that git annex is used
Applied. Thank you.
I added TINYCHANGE at the end of the commit message since you don't
appear to have signed FSF papers. Please
Vaidheeswaran C writes:
> 1. "New citation syntax" is concerned with ORG SYNTAX
>
> 2. oc.el is concerned with EDITING org files.
>
> 3. ox-jabref.el (and others) is concerned with DOCUMENT CREATION.
True.
> It seems like your plan is to put 1, 2 & 3 ALL TOGETHER in
> trunk. i.e., ALL or NONE.
Titus von der Malsburg writes:
> The reason why I think this would be useful is that some simple things
> are currently not possible. Consider the following document structure:
>
> * Office
> ** To do
> ** Finished
> * Home
> ** To do
> ** Finished
>
> If I want to archive things und
On Wednesday 13 May 2015 04:32 PM, Nicolas Goaziou wrote:
> Vaidheeswaran C writes:
>
>> On Sunday 10 May 2015 12:44 PM, Nicolas Goaziou wrote:
>>
>>> It will land in the trunk once a library using it for Org core is
>>> implemented. I put it in a separate branch so that such a library can be
>>>
46 matches
Mail list logo
