On Tue, 17 Dec 2019 at 18:13, William Denton wrote:
> On 17 December 2019, Vikas Rawal wrote:
>
> > A simple code block like the following does not create the graph.
> >
> > #+NAME: test
> > #+BEGIN_SRC R :results output graphics :exports results :file temp.jpg
> :width 2400 :height 1200 :res
I'd like to add a vote for the old behavior. I only recently noticed the
new behavior, and agree with Richard that it's inconvenient. I think
many of us missed this change because it wasn't in 9.2.
In particular, I'd propose to make the old behavior the default, and
hide the new behavior behind
On 17 December 2019, Vikas Rawal wrote:
A simple code block like the following does not create the graph.
#+NAME: test
#+BEGIN_SRC R :results output graphics :exports results :file temp.jpg :width
2400 :height 1200 :res 300 :session temp
That should be ":results file graphics".
Bill
--
Hello Bastien,
Nice to see you are still alive ;)
Sad to read that you plan to stepdown, but, happy to finally have a way
to support your work on a regular basis.
I hope you will continue to be part of this community even as an humble
user ;).
And I hope, everything will be better for you in
I have a strange problem and I wonder if there is a new bug. Would
appreciate for any help in identifying the problem.
A simple code block like the following does not create the graph.
#+NAME: test
#+BEGIN_SRC R :results output graphics :exports results :file temp.jpg
:width 2400 :height 1200
Hello,
another...@gmail.com (Nicolò Balzarotti) writes:
> The problem happens on ox-odt, when the file OrgOdtStyles.xml
> permissions are read-only (this is true especially for Guix and Nix
> where all the "store" is readonly). The file gets copied to /tmp/ob-*/
> directory, and is then
Hello,
Ben Polson writes:
> Specifically with this example formula:
> ‘@3 = 2 * remote(FOO, @@1$$#)’
>
> As I've been playing around with tables and formulas I've come to the
> conclusion that '@@1' must be a typo, and that what was intended was just
> '@1'. I have a few qualms about this table
Sorry for the noise, but I just had another thought:
Rather than adding a new option, how about we make the behavior
dependent on the value of org-src-window-setup?
Basically, when org-src-window-setup is current-window, it never makes
sense to restore the original layout. But when
On Tuesday, 17 Dec 2019 at 06:28, Jack Kamm wrote:
> Basically, when org-src-window-setup is current-window, it never makes
> sense to restore the original layout. But when org-src-window-setup is
> reorganize-frame (the default), it always makes sense to restore the
> original layout.
This makes
Hi Michael,
Michael Heerdegen writes:
> Would you consider to do something like this by default?
I guess you're asking me, since I'm the only other person in this
thread--but I'm not an Org maintainer, so my opinion isn't very
important. IMO, the hooks are worth considering, however they
> On Dec 16, 2019, at 1:53 PM, Michael Gauland wrote:
>
> I've just started playing with #+INCLUDE, so I may not be using it correctly,
> but this works for me.
Indeed, if what the OP wants is to wrap just that code as a src block and
export it and any results it produces during export
Michael Heerdegen writes:
> Adam Porter writes:
>
>> I guess you're asking me, since I'm the only other person in this
>> thread--but I'm not an Org maintainer, so my opinion isn't very
>> important. IMO, the hooks are worth considering, however they should
>> be done very, very carefully,
Adam Porter writes:
> I guess you're asking me, since I'm the only other person in this
> thread--but I'm not an Org maintainer, so my opinion isn't very
> important. IMO, the hooks are worth considering, however they should be
> done very, very carefully, because bad things can happen when
It's currently possible for me to create two meeting times, one from 8:00-10:00
tomorrow and the other from 9:00-11:00 tomorrow.
When both are mentioned in the same sentence, as above, it's easy to recognize
that the two meetings are probably incompatible. But org-mode allows agenda
items to
i might be completely off on this, but it seems the problem is that
there is a corrupted buffer.
in particular, there is a missing newline at the end of the narrowed
region in the capture buffer. this causes the next header to join the
last line in the captured buffer.
i encountered this
>> That should be ":results file graphics".
>>
>>
> Thanks very much. This works. I guess this has recently changed. I have
> always used ":results output graphics"
>
>
>
I see that the behaviour changed with 9.3. Release notes (
https://www.orgmode.org/Changes.html) have this:
:file header
Michael Heerdegen writes:
> Adam Porter writes:
[...]
>> I haven't seen your bug report. Was there discussion about it
>> previously?
>
> No, no discussion at all. As I said, it is Emacs bug #37890, this was
> my issue:
>
> | I want to capture an APPT with `org-capture'. I the pop-up buffer
Hi,
Here is the updated patch, including the fix to only trigger on
actual headlines (and not bold or similar), the readability
improvement for beg-of-next-line and a fix to call point-max only once
per branch. I also switched all the regex over to use the rx macro. I
left out the tests
On Tuesday, 17 Dec 2019 at 17:07, Samuel Wales wrote:
> i encountered this problem today. i added a task and duplicated it.
> this caused the corruption. it also screwed up the stars level, but
> never mind that.
I've encountered the problem in the past week or two when I was tweaking
one of my
On Tuesday, 17 Dec 2019 at 14:05, David Rogers wrote:
> Is there any method to get org-mode to alert me (by an error message,
> or a red mark in the agenda, or whatever) that I've created a conflict
None that I know of. I've trained myself to only create meetings from
the agenda view for this
Dear Michael,
> BTW, what is the canonical place to report org-mode bugs? Emacs bug
> reports are not (takes a long time until someone even notices) -- I
> thought this list would be good...or is there a better place? @Adam
> it's ok if you answer, though I'm a bit disappointed that no one
21 matches
Mail list logo
