On 02/07/14, 07:18 , John Hendy wrote:
> Greetings,
>
>
> I don't usually tangle, but am creating a code file to go along with a
> presentation I'm giving this weekend so that attendees can try things
> out afterward by cloning my github repo where all the data and
> necessary files are stored.
Hello,
Eric Schulte writes:
> For a while now I've been wishing that keywords (namely #+Caption:)
> could be equivalently specified as blocks (e.g., #+begin/end_Caption:).
>
> Would that be another possible solution here?
That would defeat the purpose of the distinction between a block and an
a
Hi all,
Nicolas Goaziou writes:
> I'm sure this idea wouldn't be a net benefit for Org syntax clarity,
> even for the occasional three lines caption need.
I agree.
Nicolas, what do you think of enhancing the auto-filling (and
delete-indentation) capabilities for some affiliated keywords?
#+CA
Hello,
Bastien writes:
> I see that turning a commented line is prevented, while turning
> several commented lines is allowed. This feels weird. I don't
> think we should prevent this.
>
> What do you think?
I don't think there's much point in comparing function's behaviours when
acting on a
Nicolas Goaziou writes:
> Anyway, in this particular case, I guess we could consider comments as
> a stack of one line elements. I added the feature.
Thanks!
--
Bastien
Hello,
> Nicolas, what do you think of enhancing the auto-filling (and
> delete-indentation) capabilities for some affiliated keywords?
>
> #+CAPTION:
> #+HEADER:
> #+TBLFM:
Not that it matters much, but "TBLFM" is not an affiliated keyword per
se, it belongs to the table syntax. OTOH, you can ha
Hello,
Nicolas Goaziou writes:
> Hello,
>
>> Nicolas, what do you think of enhancing the auto-filling (and
>> delete-indentation) capabilities for some affiliated keywords?
>>
>> #+CAPTION:
>> #+HEADER:
>> #+TBLFM:
>
> Not that it matters much, but "TBLFM" is not an affiliated keyword per
> se,
Andreas Leha writes:
> But here an obvious
> 'solution' would be to move the short caption to #+SHORT_CAPTION.
Yes. #+CAPTION[...]: is clumsy.
--
Bastien
Bastien writes:
> Yes. #+CAPTION[...]: is clumsy.
It follows #+RESULTS[...]: model.
--
Nicolas Goaziou
The purpose is to be polite with minor modes and to not use
C-c [:punct:] keybindings, as recommended in the Elisp manual.
This is related to the issues reported here:
http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg00866.html
http://article.gmane.org/gmane.emacs.orgmode/82010
Here is
Hi,
Nicolas Goaziou writes:
> Why this suggestion?
To get Emacs core maintainers opinions on this and clarify if we can
expand Org features at will or if they want to be control that somehow.
> We recently introduced "ob-coq.el" in core without
> asking Emacs maintainers beforehand.
That's di
Bastien writes:
> Hi Alan,
>
> Alan Schmitt writes:
>
>> I tried it and it does not change anything on worg.
>
> The purpose of the patch is so that C-c C-l on a headline
> will then insert a link without escaping whitespaces:
>
> * Headline with whitespaces
>
> [[*Headline with whitespaces][Hea
Hello,
Bastien writes:
> My suggestion is to ask Emacs maintainers
Why this suggestion? We recently introduced "ob-coq.el" in core without
asking Emacs maintainers beforehand.
Regards,
--
Nicolas Goaziou
Dear org-mode Developers and Users,
(Org-mode version 8.2.5g from git)
I want to change the behaviour of C-c ' when inside a source block.
What I am after is best described in a schematic:
+---+---+
| | |
| | 2 |
Bastien wrote:
> The purpose is to be polite with minor modes and to not use
> C-c [:punct:] keybindings, as recommended in the Elisp manual.
>
> This is related to the issues reported here:
> http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg00866.html
> http://article.gmane.org/gmane.ema
Nicolas Goaziou writes:
> Bastien writes:
>
>> Yes. #+CAPTION[...]: is clumsy.
>
> It follows #+RESULTS[...]: model.
Which I feel clumsy too :) No offense to either Eric or you.
The important difference is that #+RESULTS[...] is generated,
while #+CAPTION[...] is manually entered. As a user
Thanks for your feedback.
"Sebastien Vauban"
writes:
>> - use C-c < for selecting the whole subtree, which is consistent
>> with the use of `<' as a speedy command for doing the same.
>
> You put the finger on one important note to me: that speed commands are
> "the same" as their longer
Hi!
I am not an ELISP programmer (unfortunately) but a proud heavy-user
of Org-mode. At work, I need a REST-client to talk to a REST API
very often.
Recently, I found [1] which works quite well. However, I need to
open a new buffer into restclient-mode to execute requests.
Wouldn't it be nice if
Hi Bastien
On Fri, Feb 7, 2014 at 11:32 AM, Bastien wrote:
> | C-c # | Checkboxes| C-c x| Free |
I did not know "C-c #" (org-update-statistics-cookies) because for me
it is easier to remember and therefore I always used this: Go to
cookie and do "C-c C-c". A
Hello,
I use and abuse the `org-latex-minted-options' when exporting source
blocks in latex, but I'm stumped by a usage pattern. I need to change
the list of options for one given source block (adding a "belowskip"
option to it). I tried the following, but it did not do anything:
--8<
Hello,
Exporting this:
--8<---cut here---start->8---
- I don't see the same prices as in the tutorial: in fact, the prices of
=Simulation_1= and =Simulation_3= are inverted!
--8<---cut here---end--->8---
gives that:
--8<-
Bastien writes:
> The purpose is to be polite with minor modes and to not use
> C-c [:punct:] keybindings, as recommended in the Elisp manual.
>
> This is related to the issues reported here:
> http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg00866.html
> http://article.gmane.org/gmane.
Nick Dokos writes:
> Bastien writes:
>
>> The purpose is to be polite with minor modes and to not use
>> C-c [:punct:] keybindings, as recommended in the Elisp manual.
>>
>> This is related to the issues reported here:
>> http://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg00866.html
>> h
On Wed, Feb 5, 2014 at 12:54 PM, Wiskey 5 Alpha wrote:
> I have some projects that are 4 levels deep, so this is quite annoying. How
> do
> I get just the "deepest" level project to show without it's parents ?
>
> here is my custom agenda view for projects
>
> ("p" "@Projects" tags-todo "-IGNORE-
Rainer M Krug writes:
> On 02/07/14, 07:18 , John Hendy wrote:
>> Greetings,
>>
>>
>> I don't usually tangle, but am creating a code file to go along with a
>> presentation I'm giving this weekend so that attendees can try things
>> out afterward by cloning my github repo where all the data and
Bastien writes:
> To get Emacs core maintainers opinions on this and clarify if we can
> expand Org features at will or if they want to be control that
> somehow.
AFAICT, we never asked Emacs maintainers before adding a feature to Org,
and I don't think the number of export targets in core grew
Hi,
around the org-mode 8.0 release I began to write a new blog exporter
using the new export framework.
I wanted one feature org2blog didn't offer, support for different syntax
highlighters, and i wanted to learn about the new exporter and Emacs
programming.
Around Christmas I did some polishin
On Fri, Feb 7, 2014 at 5:29 AM, Michael Bach wrote:
> Dear org-mode Developers and Users,
>
> (Org-mode version 8.2.5g from git)
>
> I want to change the behaviour of C-c ' when inside a source block.
> What I am after is best described in a schematic:
>
> +---+---+
> |
Nicolas Goaziou writes:
>> That's different: supporting as many programming languages is a core
>> feature of Babel, while supporting as many export target as possible
>> should not be a core feature of Emacs IMO, it should stay as a nice
>> facility of the Org ecosystem.
>>
>> The second part of
Robert Klein writes:
> Hi,
>
> around the org-mode 8.0 release I began to write a new blog exporter
> using the new export framework.
>
> I wanted one feature org2blog didn't offer, support for different syntax
> highlighters, and i wanted to learn about the new exporter and Emacs
> programming.
Aloha all,
Nicolas Goaziou writes:
> Bastien writes:
>
>> To get Emacs core maintainers opinions on this and clarify if we can
>> expand Org features at will or if they want to be control that
>> somehow.
>
> AFAICT, we never asked Emacs maintainers before adding a feature to Org,
> and I don't
i'd like to point out that some of these bindings are problematic on
qwerty in a way that is not obvious to many users.
many people use shifting keys on both sides of the keyboard.
they do not issue the control of control g using left hand. that is a
bad idea. instead, they hold down the right
Hello,
"Sebastien Vauban"
writes:
> Exporting this:
>
> - I don't see the same prices as in the tutorial: in fact, the prices of
> =Simulation_1= and =Simulation_3= are inverted!
>
> gives that:
>
> • I don’t see the same prices as in the tutorial: in fact, the prices
> of `Simulatio
On 02/07/14, 17:47 , Eric Schulte wrote:
> Rainer M Krug writes:
>
>> On 02/07/14, 07:18 , John Hendy wrote:
>>> Greetings,
>>>
>>>
>>> I don't usually tangle, but am creating a code file to go along with a
>>> presentation I'm giving this weekend so that attendees can try things
>>> out afterw
Hi Rasmus,
thank you very much for your feedback!
On 02/07/2014 06:35 PM, Rasmus wrote:
> Could you provide an example blog so that we can see the output?
The two latest posts ("FreeBSD" and "DHCP") at http://www.xyzzy.de/
I put the original org for download at the end of both posts.
>> ;;;
Bastien writes:
> Hi all,
>
> Nicolas Goaziou writes:
>
>> I'm sure this idea wouldn't be a net benefit for Org syntax clarity,
>> even for the occasional three lines caption need.
>
> I agree.
>
> Nicolas, what do you think of enhancing the auto-filling (and
> delete-indentation) capabilities f
Eric Schulte writes:
> See the attached example file. This is very rudimentary, only
> supporting session evaluation and without support for smart translation
> between Org-mode and Coq data structures.
Very nice, thanks a lot!
I use org mode with Coq, but only to document Coq developments. Se
Hello,
Alan Schmitt writes:
> I use and abuse the `org-latex-minted-options' when exporting source
> blocks in latex, but I'm stumped by a usage pattern. I need to change
> the list of options for one given source block (adding a "belowskip"
> option to it). I tried the following, but it did not
I know there is a way to display parent headlines using the agenda
prefix.
Is there a simple way to do this conditionally for certain subtrees?
Here's my use case. I have an org file machines.org for keeping track of
what I do to various machines I work on/administer (though I use that
term hesit
John Hendy gmail.com> writes:
>
> An interesting update on this. Aside from some image and code block
> stuff, the following works surprisingly well!
> - Export Org -> markdown (md)
> - Start an R session and `setwd("/path/to/file.md")`
> - Run `library(slidify)` and `author("deck")
> - Copy the
Hi, Bastien,
If it's difficult to keep dragging from moving hidden lines,
I agree, `/ /' removing the re-ordering would be less confusing
than seeing the hidden lines moved.
By the way, another useful feature could be dragging all lines
in the region if it's active.
Thanks,
Thomas
Hi Robert,
On Fri, 7 Feb 2014, Robert Klein wrote:
around the org-mode 8.0 release I began to write a new blog
exporter using the new export framework.
I wanted one feature org2blog didn't offer, support for different
syntax highlighters, and i wanted to learn about the new exporter
and Emac
John Hendy gmail.com> writes:
>
> On Fri, Feb 7, 2014 at 3:50 PM, Charles Berry ucsd.edu> wrote:
> > John Hendy gmail.com> writes:
> >
> >>
> >> An interesting update on this. Aside from some image and code block
>
[snip - how John turn org to Rmd to md]
> >
> > John,
> >
> > You can put the
Is there a way to hide done/ cancelled items?
I have ** A Project and lots of *** items that are done and I want to hide
to avoid distractions. After the project is done, I will move the ** A
Project along with all the *** items to the _archive file.
Thanks.
On Fri, Feb 7, 2014 at 11:38 PM, John Hendy wrote:
> On Fri, Feb 7, 2014 at 7:04 PM, Charles Berry wrote:
[snip]
> I'll look into those. I just cloned your repo and loaded ox-ravel.
> Quite nice! It worked /pretty/ well out of the box. One issue is that
> it doesn't seem to obey :eval no for ba
45 matches
Mail list logo
