I could start a document out with a table and maybe write some text
outside of that table below it but then I would need to write a
different table below that text with different column headings and
different content.
If necessary, I could also write one table per document and text in
separate
You mean besides something like:
| a | b |
|---+---|
| 2 | 3 |
Some text
#+name: some-ther-table
| x | y |
| 4 | 5 |
| 7 | 8 |
etc...
Jude DaShiell writes:
> First, can it be done?
> Second, can I write text between tables in the document?
> Third, can I start a table after first line of
First, can it be done?
Second, can I write text between tables in the document?
Third, can I start a table after first line of document and also end that
table?
Earlier I wanted to write a document containing notes and tables and found
it difficult getting emacs-orgmode to end the first
Hello,
Achim Gratz writes:
> No, we shouldn't. It's either automatic or a release, it can't be
> both.
I can't see why. We already "release" automatically new packages.
> Also, the releases are distinct from the ELPA packages and you seem to
> mix up the two. They are not
On 1 November 2016 at 17:01, Bastien Guerry wrote:
>
> Let me know if the current page is at least 90% "good enough" :)
>
You can have your 90% rating now!
Thanks very much for engaging with my criticism to improve things!
--
http://rrt.sc3d.org
On 2016-10-29 15:37, John Kitchin writes:
> On the org-mode mailing list there was some discussion about sending
> html mail using orgmode. The support for this in mu4e is deprecated.
> There is the org-mime library though, and it supports a lot of what is
> needed for
Nicolas Goaziou writes:
> This is not what I'm suggesting. Let me try to expunge a bit.
>
> I thing we should automate bugfix releases with regular version
> numbering scheme, e.g., 8.3.7 release, /as a replacement for/
> org-MMDD releases. Therefore:
No, we shouldn't. It's either automatic
Nicolas Goaziou writes:
> Evaluate the following function (C-x C-e) and test again.
Debugger entered--Lisp error: (error "Match data clobbered by buffer
modification hooks") replace-match(#(" :LAST_REPEAT: [2016-11-01 Uto
18:02]" 0 3 (fontified nil) 3 4 (fontified
Hi,
Reuben Thomas writes:
> 1. The top heading is "Download and install", but the second half of
> the section is a list of links that look like they belong in a
> different section (List of features, Manuals and tutorials…).
I could not find an elegant solution for this. I
We might not always want a full export of an org heading to html for sending an
email. Eric Brown would like to just send something that looks like what he
sees in org-mode. There is another way to get html from emacs: htmlize! Here is
an example. Eric: if this is what you mean, see my modified
Hi Nicolas,
Nicolas Goaziou writes:
> I thing we should automate bugfix releases with regular version
> numbering scheme, e.g., 8.3.7 release, /as a replacement for/
> org-MMDD releases.
Okay.
> Therefore:
>
> 1. org-MMDD could be renamed
Saša Janiška writes:
> Not sure how I’m supposed to do it? Writing some custom function?
> Where?
Evaluate the following function (C-x C-e) and test again.
(defun org--align-node-property ()
"Align node property at point.
Alignment is done according to
Nicolas Goaziou writes:
> Does wrapping `org--align-node-property' within `save-match-data' solve
> the problem?
Not sure how I’m supposed to do it? Writing some custom function? Where?
Sincerely,
Gour
--
One who restrains the senses of action but whose mind dwells
John Kitchin writes:
> Do you mean monospace in the whole html message, e.g. something like Courier?
>
> Or just in a table? I do not think you can control the font in plain
> text emails.
>
> You can set the font in the td elements of a table like this (I used
> cursive
Hi Nicolas,
Checked with the latest org (release_8.3.6-1267-g58dbdb), and it still
shows the source block face when collapsed.
Org-ellipsis face and text can be customised though. See attached
screenshot.
Adding an empty line after the block does fix it, so it is really just an
aesthetic nitpick
Hello,
Saša Janiška writes:
> Saša Janiška writes:
>
>> This Org mode version 8.3.6 (release_8.3.6-1267-g58dbdb @
>> /home/gour/.emacs.d/lisp/org/) is master, right?
Correct.
> I had enough of this problem and, for now, the most easy workaround is
> to
Saša Janiška writes:
> This Org mode version 8.3.6 (release_8.3.6-1267-g58dbdb @
> /home/gour/.emacs.d/lisp/org/) is master, right?
I had enough of this problem and, for now, the most easy workaround is
to simply downgrade Emacs to 24.5.1 where *everything* works as
intended.
Hello,
Bastien Guerry writes:
> We could simply have daily snapshot of the maint branch in addition to
> daily snapshot of the master branch.
>
> For now http://orgmode.org/org-latest.tar.gz is build from the master
> branch, but we could also have
On 1 November 2016 at 10:32, Bastien Guerry wrote:
> Hi,
>
> I changed the order of presentation for installation methods on the
> website, promoting Org ELPA method.
>
That's much better, thanks.
However, I still find the first section of the main page rather confusing.
I
Hi,
I changed the order of presentation for installation methods on the
website, promoting Org ELPA method.
Thanks,
--
Bastien
Hi all,
Nicolas Goaziou writes:
> However, I think we should make more frequent bugfix releases. We may
> even automate such releases, e.g., one week after the last unreleased
> bugfix in the branch. I don't do releases however, so this may just be
> a weird idea.
>
>
Nicolas Goaziou writes:
> There are 1200+ commits in the master branch that are not in the stable
> one. It could make a difference.
It does not. :-(
This Org mode version 8.3.6 (release_8.3.6-1267-g58dbdb @
/home/gour/.emacs.d/lisp/org/) is master, right?
Sincerely,
Hello,
"Bruce V. Chiarelli" writes:
> 2016-10-31 17:04 GMT-07:00 Nicolas Goaziou :
>> Does adding the following branch in the `cond' above, before the
>> catch-all one, solve the issue?
>>
>> ((eq origin-cat 'after) (match-end 0))
>
> It does!
Hello,
Maciek Starzyk writes:
> Not sure if this is a bug or a feature:
> Collapsed sections, which end with a source code block, have the same font
> (from the ellipsis until the end of line) as the code block last line. The
> face name is `org-block-end-line'.
> This
24 matches
Mail list logo