[O] can't assign to hline relative reference:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear list, Consider the following small org table: | | grade | weight | weighed grade | |---+---++---| | | 5 | 10 |50 | |---+---++---| | total | || 0 | #+TBLFM: @II$2=vsum(@I$2..@II-1$2)::$4=$2*$3 In the version of org (8.2.10) distributed with emacs 24.5, evaluating this table does not produces the expected result of column 2 being summed to a total of 5. Instead depending on point both the second and first columns will get an additional 5. Through irc I found someone who tested this with the latest development version as of now and it instead produces the error: can't assign to hline relative reference. That also does not seem like the right behavior to me. Could someone shed some light on the situation? Marijn -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlWNQasACgkQp/VmCx0OL2yYagCgwLUWq7sP/GhJAfkwajCAvHRP u+kAmwcV1GjT0Lbyo0Mrj6F87q+e/uib =wIrP -END PGP SIGNATURE-
Re: [O] can't assign to hline relative reference:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26-06-15 14:22, Nicolas Goaziou wrote: Hello, Marijn Schouten (hkBst) hk...@gentoo.org writes: Through irc I found someone who tested this with the latest development version as of now and it instead produces the error: can't assign to hline relative reference. That also does not seem like the right behavior to me. Could someone shed some light on the situation? See http://article.gmane.org/gmane.emacs.orgmode/77257. Regards, Thanks Nicolas for that link. It says that there is a known issue with hline references on the left side of table formulas, but I did not quite understand the details. There seems to be a proposed fix by interpreting said references as ranges with the same on both sides, for example @II$2 would become @II$2..@II$2 and would then be interpreted properly. Was the issue with this fix that it does not work in all cases? There also seems to be some counterintuitive use of these references that is useful to some people and included in the tests and fixing the issue would interfere with that use. If I said that right, could someone explain the details of this? There was a mention that fixing the issue might involve rewriting much of org-table. Is that a concern? Marijn -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlWNTMoACgkQp/VmCx0OL2yt1ACZAcFxBtcRwhZ6IPPA02xZtrSk 9xEAn3aY1JKYJkoy1bzhOV4mFbc8UDz7 =0uQ0 -END PGP SIGNATURE-
Re: [O] latex-export of first-column-starting emphasis broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16-01-13 20:50, Nick Dokos wrote: Marijn hk...@gentoo.org wrote: While visiting a file with just these two lines: * S /s ()/ export to latex: C-c C-e p. Resulting tex file fails to compile due to the presence of: \emph{s ()\} instead of \emph{s ()} If you add a space to the beginning of the second line, then it works as expected. I am using this work-around for now. I'm using emacs-24.2 I think the problem was that I was using the org-mode that's included with emacs-24.2 (version 6 something?). Using a more recent external version I also cannot reproduce the problem. Thank to you both for testing and sorry for the noise. Marijn -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEkirUACgkQp/VmCx0OL2zOWwCfXIflOHqgF4Fe4cwtWrDRtHCn cwAAnRdRhAy79MylqKN8K58IwNW5F0+o =XXjb -END PGP SIGNATURE-
[O] latex-export of first-column-starting emphasis broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 While visiting a file with just these two lines: * S /s ()/ export to latex: C-c C-e p. Resulting tex file fails to compile due to the presence of: \emph{s ()\} instead of \emph{s ()} If you add a space to the beginning of the second line, then it works as expected. I am using this work-around for now. I'm using emacs-24.2 Marijn PS Please CC me in responses, as I'm not subsscribed. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlD2zTsACgkQp/VmCx0OL2yGBQCfWJ1XxQOzZvLRNkepyC8GbI2G SOAAoKKgVv2fgouo/7ZjChSPztiIkHaC =i1dg -END PGP SIGNATURE-