Re: [O] new latex exporter and attr_latex
> Yes, the syntax has changed; see > http://thread.gmane.org/gmane.emacs.orgmode/62766 > > In short, you should use: > #+ATTR_LATEX: :align lcr > > Kind Regards, > Mike Thanks. It works like that. Best thoughts, François
Re: [O] info for org not found in emacs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/12 11:29, Jambunathan K wrote:
> Rainer M Krug writes:
>
>> On 10/12/12 23:15, Charles wrote:
>>> On 12/10/2012 12:43 PM, Eric Schulte wrote:
Rainer M Krug writes:
> On 10/12/12 17:50, Jambunathan K wrote:
>> Rainer M Krug writes:
>>
>>> Thanks - does anybody else has any ideas on how I can get org into info?
>> M-x info-display-manual RET ~/src/org-mode/doc/org RET
>>
> This definitely works - thanks. But is there a way of adding this
> permanentely, so that
> I can use the menu entry in the org menu to see the info file?
>
The following works for me (your mileage may vary)
;; info paths (add-to-list 'Info-default-directory-list
"/home/eschulte/.emacs.d/src/org-mode/doc/")
>>
>> This did not work.
>>
>>> For my set up (see below) I have tried Eric's suggestion, except
>>> "/home/Charlie/elisp/org-mode/doc/"
>>>
>>> I have also tried (expand-file-name "~/elisp/org-mode/doc/") (I found this
>>> in the FAQ)
>>>
>>> "C-h v Info-default-directory-list" shows that
>>> "/home/Charlie/elisp/org-mode/doc" loads
>>> before all other info directories.
>>>
>>> Info at the command line and "C-h i" from Emacs still bring up the manual
>>> for 7.9.1 even
>>> though the 7.9.2 org.doc has been downloaded. . . . . . . . . . . . . After
>>> writing the
>>> above I went back to the FAQ and added the following to my ~/.bash_profile
>>>
>>> INFOPATH=/home/Charlie/elisp/org-mode/doc/
>
> How about customizing `Info-additional-directory-list' without touching
> INFOPATH as suggested
> below?
That is working - thanks. It is the better way then modifying the INFOPATH
userwide.
Strange that changing the Info-default-directory-list did not work.
Cheers,
Rainer
>
> , | Info-default-directory-list is a variable defined in `info.el'. | Its
> value is
> ("/usr/local/share/info/" "/usr/share/info/") | | Documentation: | Default
> list of directories
> to search for Info | documentation files. They are searched in the order
> they are given in |
> the list. Therefore, the directory of Info files that come with Emacs |
> normally should come
> last (so that local files override standard | ones), unless Emacs is
> installed into a
> non-standard directory. In | the latter case, the directory of Info files
> that come with
> Emacs | should be first in this list. | | Once Info is started, the list of
> directories to
> search comes from the | variable `Info-directory-list'. This variable |
> `Info-default-directory-list' is used as the default for initializing |
> `Info-directory-list'
> when Info is started, unless the environment | variable INFOPATH is set. | |
> , | | , |
> | | Although this is a customizable variable, that is mainly for | | |
> technical reasons.
> Normally, you should either set INFOPATH or | | | customize
> `Info-additional-directory-list',
> rather than changing | | | this variable. | | ` | ` | | You can
> customize this
> variable. `
>
>
>
>
>
>
>> I added this to the .bashrc and it is working now.
>>
>> Thanks,
>>
>> Rainer
>>
>>>
>>> It works for info from the command line. As a matter of fact the new org
>>> info is at the
>>> beginning of the info contents. However emacs C-h i only bring up the Org
>>> info, even
>>> though "C-h v Info-default-directory-list" shows that all info directories
>>> are loaded.
>>>
>>> Set up: Windows 7 Home Premium, Service Pack 1, 64 bit Cygwin 1.7.17-1 GNU
>>> Emacs
>>> 24.2.1(i686-pc-cygwin, GTK+ Version 2.24.11) of 2012-08-27 on fiona
>>> Org-mode version 7.9.2
>>> (release_7.9.2-664-gb1f369 @ /home/Charlie/elisp/org-mode/lisp/)
>>>
>>> Charlie Millar
>>>
>>>
>>
>
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys.
(Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D):+49 - (0)3 21 21 25 22 44
email: rai...@krugs.de
Skype: RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlDIaTIACgkQoYgNqgF2egrpLACfTnzUOidmNH9urOhcOePWTb7T
SUEAn2u3ObN0rX+JkILBKkYaE8PxNMa/
=PxHi
-END PGP SIGNATURE-
Re: [O] Agenda: show only prio-A events with associated date/timestamp
* Memnon Anon wrote: >>> I'd like to derive a custom agenda view that has following properties: >>> >>> - show only items with associated datestamp or timestamp (same as >>> «is displayed in the time grid of my usual agenda») >>> - only with priority [#A] > > So, your usual agenda, but only priority #As ? ... and without todos that are do not have an associated date/time. Yes. > Or only those items with stamps that don't only signify a day but also a > time(-range)? - items with stamps or time or time-ranges (not including DEADLINE/SCHEDULED or date/time/ranges in the "body" of the item) AND - items with prio #A >> If it is possible to differ between associated datestamps/timestamps >> and deadlines/schedules, I'd prefer following: >> Examples: >> >> * shown::shown: >> ** TODO <2012-12-11 Tue> todo with date > > Why should this one be shown? It is not [#A]? Absolutely. My fault :-( The idea behind this request is: only the most important milestones and events get priority A. This way, I am able to get a quick overview of a large period of time without much distraction. On my wall calendar, there are only approx. 5-10 of such A-events per month. Whereas on a normal day, I do have 5-10 (non-prio) events. Therefore I kept my wall calendar in order to get an overview. But I want to get rid of physical tools like this. -- Karl Voit
Re: [O] Bug: export to LaTeX doesn't handle filenames properly [7.8.11]
Hi John, John Smith writes: > I have in my .org file links to files that contain spaces and []. > org-insert-link converts space to %20, [ to %5B, ] to %5D. Fixed for the current exporter, I didn't check with the new LaTeX exporter. Thanks for reporting this, -- Bastien
Re: [O] babel perl issue
Eric Schulte gmail.com> writes: > I will make this change (in fact I had done this originally, but then > didn't want to send too many patches so I compressed the commit > history). It just occurs to me that it would be even better if you copied the file verbatim instead of renaming it as the very first step. That way the history is preserved across both files since the SHA1 for both files is the same at that commit. Then just reset the tree to the commit where you had edited the files (the first one in your two part series) and commit that set of changes. Then cherry-pick part two. > Each language file will only need to (require 'ob), only a few of the > core Babel files would actually require ob-core. Here's a diagram of > the require structure. :-) Regards, Achim.
Re: [O] source code disappears
On 17/11/2012 12:41, Bastien wrote: Hi Andy, Andy Moreton writes: When I switch to the ELPA version ( "Org-mode version 7.9.2 (7.9.2-82-g2aeb28-elpa @ . . . )") this misbehavior is corrected. HTH. I've filed emacs bug#12905 about this, as it is occurring in on the emacs-24 branch, and emacs 24.3 is getting close to release. Can somebody please update org mode in emacs to bring it up to date. I will take care of this before the end of the pretest week. Hi Bastien, I haven't seen this merge appear on the emacs-24 branch yet - any idea when you will have time to do the merge ? Thanks, AndyM
Re: [O] new latex exporter and attr_latex
Hello, François Allisson writes: > Le mardi 11 décembre 2012 à 17h47, Nick Dokos a écrit: >> See >> >> http://thread.gmane.org/gmane.emacs.orgmode/62766 >> > > Thanks Nick! > > #+attr_latex: :align lcr Or, perhaps better, since it will work across all export back-ends: | | || | left | center | right | Regards, -- Nicolas Goaziou
Re: [O] Formatting Text in Org-mode
Hi Rodolfo, Rodolfo Aramayo writes: > In org-mode, writing: /matA^HMG/ would be incorrect because the > superscript 'HMG' should NOT be italics The new exporter handles this correctly. If you installed Org from http://orgmode.org/org-7.9.2.tar.gz add the contrib/ directory to your load-path then (require 'org-export) (require 'org-e-latex) and M-x org-e-latex-export-to-latex in the Org buffer. Otherwise wait for Org 8.0 to be released. HTH, -- Bastien
Re: [O] org-capture vs. org-agenda-capture
Hi Rene,
Rene writes:
> On the other hand, when calling org-agenda-capture ('k' from the agenda), your
> timestamps always indicates a null time [2012-12-11 Tue 00:00].
>
> Is there a way I can force org-agenda-capture to indicate the current
> time?
>From latest git, you can use `C-1 k' to use the time of the current line
or the current time.
Thanks for triggering this change!
--
Bastien
Re: [O] org-sync doesn't work with recent org-element.el
Hi Jonas, I'm copying Aurélien, the author of org-sync. Aurélien, are you willing to maintain org-sync or shall we call for a new maintainer? Thanks for your answer! Best, -- Bastien
Re: [O] Is it possible to see the blocking task?
Hi Mirko, Mirko Vukovic writes: > I'd like to see the blocking task in order to "debug" my setup. >From latest git (master) the error message you get now contains the name of the blocking entry. HTH, -- Bastien
Re: [O] clock-in task is not highlighted in agenda view
Hi Liang, Liang Wang writes: > When I press 'I' to clock-in task in agenda view, the line of that > task is not highlighted any more. Just to confirm this has been fixed. Thanks, -- Bastien
Re: [O] babel perl issue
Hi Eric, Eric Schulte writes: > Please let me know if I can explain anything, or if you'd like to see > the patches before the hit the master branch. I've read the thread carefully and I cannot clearly see what problem we are trying to fix. I acknowledge things can be cleaned up somehow, but I need to see the actual bug that we are fixing here... see my reply to Achim in the same thread. Thanks, -- Bastien
Re: [O] babel perl issue
Hi Achim, Achim Gratz writes: > Eric Schulte writes: >> See http://orgmode.org/manual/Languages.html for the documentation on >> how to activate and disable org-babel languages. > > That actually produces the error: > > File mode specification error: (void-variable org-babel-tangle-lang-exts) > > as the OP has found out (and I can reproduce it). > > The reason is that none of the ob-.el files do a (require > ob-tangle), but try to change a defcustom in ob.tangle.el that is only > declared, but not yet available at the time. I've quickfixed it by > moving the require for ob-tangle in org.el to the beginning of the file, > but this is now relying on the fact that org is implicitly loaded for > getting the major mode set up, so all the babel language files still > need to be cleaned up. I can't reproduce this. I have a ~/emacs.el file containing (org-babel-do-load-languages 'org-babel-load-languages '((perl . t))) then ~$ emacs -Q -l ~/emacs.el loads correctly and `org-babel-load-languages' is correctly set up. Thanks for any help on reproducing the problem! -- Bastien
Re: [O] babel perl issue
Bastien writes: > Hi Eric, > > Eric Schulte writes: > >> Please let me know if I can explain anything, or if you'd like to see >> the patches before the hit the master branch. > > I've read the thread carefully and I cannot clearly see what problem > we are trying to fix. I acknowledge things can be cleaned up somehow, > but I need to see the actual bug that we are fixing here... see my > reply to Achim in the same thread. > This is refactoring not bug fixing. The most important impact is that this will provide for simpler requires by the files implementing support for particular languages. Rather than having to do piecemeal requires of those portions of the Babel infrastructure which may be needed locally they can simple (require 'ob) and bring in all of the Babel support as a single unit. Prior to this change there are language specific files which are using tangle defcustoms which have not been required and thus are not in scope. Finally this consolidates Babel defcustoms into ob.el where they will be more immediately brought into scope, and are more easily maintained. -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] babel perl issue
Hi Eric, Eric Schulte writes: > This is refactoring not bug fixing. The most important impact is that > this will provide for simpler requires by the files implementing support > for particular languages. Rather than having to do piecemeal requires > of those portions of the Babel infrastructure which may be needed > locally they can simple (require 'ob) and bring in all of the Babel > support as a single unit. I agree with the simplification if it does not involved creating ob-core.el and ob-customs.el. Merging ob.el and ob-tangle.el (and perhaps ob-eval.el and ob-comint.el) is a good simplification option IMHO. > Prior to this change there are language specific files which are using > tangle defcustoms which have not been required and thus are not in > scope. Got it. > Finally this consolidates Babel defcustoms into ob.el where they will be > more immediately brought into scope, and are more easily maintained. Yes, if you merge the files; otherwise, I'd stick to the namespace rule: defcustoms belong where their namespace indicate they belong. Thanks, -- Bastien
Re: [O] babel perl issue
Bastien writes: > I can't reproduce this. You most likely can if you just customize org-babel-load-languages. > I have a ~/emacs.el file containing > > (org-babel-do-load-languages > 'org-babel-load-languages > '((perl . t))) > > then ~$ emacs -Q -l ~/emacs.el loads correctly and > `org-babel-load-languages' is correctly set up. That only works because it pulls in org.el first. The problem is that the Babel files can't be completely self-contained w.r.t. their dependecies as that would create circular requires and there exist multiple code paths (mainly via autoloads) that pull in different parts of Org in different order. As a basic requirement all customization variables should become available before their uses in all those cases, but this can't be ensured (at least not easily) with the current structure. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
[O] bug#12905: 24.2.50; org: edit source block causes data loss
Hi Chong, Chong Yidong writes: > Could you please take a look at Bug#12905? If it causes data loss, I > think it should be fixed in the emacs-24 branch. Thanks. This is fixed, thanks for the heads up. I just merged the Org bugfix branch into emacs-24. I made one mistake: I backported Paul's fixes about whitespaces in our bugfix branch*, so those fixes are now in emacs-24 too, not in the trunk only. I hope this won't create merge conflicts. * http://orgmode.org/cgit.cgi/org-mode.git/commit/?h=maint&id=e5ea08 -- Bastien
Re: [O] babel perl issue
Eric Schulte writes: > Here's what the require structure of the core ob files will > look like after this change. If i read the graph correctly, merging ob.el ob-eval.el and ob-core.el will not create circular requires -- am I right? -- Bastien
Re: [O] source code disappears
Hi Andy, Andy Moreton writes: > I haven't seen this merge appear on the emacs-24 branch yet - any idea > when you will have time to do the merge ? Done. Sorry it took so long. -- Bastien
Re: [O] babel perl issue
Bastien writes: > Eric Schulte writes: > >> Here's what the require structure of the core ob files will >> look like after this change. > > If i read the graph correctly, merging ob.el ob-eval.el and > ob-core.el will not create circular requires -- am I right? Not correct. The result of such a merge would look like the following. <> With numerous circular requires. I understand that you find the existence of an ob-core file aesthetically unappealing. In principle I don't disagree, but in this particular case I do not see any preferable solution (including the "keep things as they are" option). If you can think of a better option I'm open to suggestions, but if not I would like to commit this change to master. Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Formatting Text in Org-mode
THANK YOU!! --Rodolfo On Wed, Dec 12, 2012 at 8:37 AM, Bastien wrote: > Hi Rodolfo, > > Rodolfo Aramayo writes: > > > In org-mode, writing: /matA^HMG/ would be incorrect because the > > superscript 'HMG' should NOT be italics > > The new exporter handles this correctly. > > If you installed Org from http://orgmode.org/org-7.9.2.tar.gz > add the contrib/ directory to your load-path then > > (require 'org-export) > (require 'org-e-latex) > > and M-x org-e-latex-export-to-latex in the Org buffer. > > Otherwise wait for Org 8.0 to be released. > > HTH, > > -- > Bastien >
Re: [O] babel perl issue
Bastien writes: > If i read the graph correctly, merging ob.el ob-eval.el and > ob-core.el will not create circular requires -- am I right? Any attempt to merge ob.el and ob-core.el will result in circular requires or (the status quo) incomplete requires. I hope you are not suggesting to put all of ob into a single file… Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] clock-in task is not highlighted in agenda view
Hi Bastien, On Wed, Dec 12, 2012 at 7:04 AM, Bastien wrote: > > Hi Liang, > > Liang Wang writes: > > > When I press 'I' to clock-in task in agenda view, the line of that > > task is not highlighted any more. > > Just to confirm this has been fixed. Glad to hear that. Thank you. > > Thanks, > > -- > Bastien
Re: [O] babel perl issue
Achim Gratz writes:
> I hope you are not suggesting to put all of ob into a single file…
Actually that's a good idea!
It should be ~170ko, quite manageable (similar to org-export.el.)
In terms of features, is any of ob-{keys/tangle/table/etc.}
useful by itself, outside ob?
How would you feel about this Eric?
--
Bastien
[O] bug#12905: 24.2.50; org: edit source block causes data loss
On Wed 12 Dec 2012, Bastien wrote: > This is fixed, thanks for the heads up. > > I just merged the Org bugfix branch into emacs-24. I can confirm the bug is fixed for emacs-24 after this merge. Thanks Bastien, AndyM
Re: [O] babel perl issue
Bastien writes:
> Achim Gratz writes:
>
>> I hope you are not suggesting to put all of ob into a single file…
>
> Actually that's a good idea!
>
> It should be ~170ko, quite manageable (similar to org-export.el.)
>
> In terms of features, is any of ob-{keys/tangle/table/etc.}
> useful by itself, outside ob?
>
> How would you feel about this Eric?
I don't like this idea at all.
I'm already heavily using page-feed (^L) characters to navigate the
existing ob-core.el. Combining all of the separate components of babel
into a single file would lose much needed separation and organization
and would make Babel harder to maintain.
In the absence of better ideas, I'm going to go ahead with this
refactoring. If we do come up with a better idea at some time in the
future I'll be happy to make further changes. Lacking that we can
always revert this change when Emacs Lisp begins to provide support for
proper modules.
Cheers,
--
Eric Schulte
http://cs.unm.edu/~eschulte
Re: [O] Some Experiences with org-babel-load-file
Florian Beck writes: > On 12/11/2012 03:52 PM, Eric Schulte wrote: > >> Please go ahead and update the information on worg. Note that Emacs24 >> users need only do >> >> (require 'org) >> (org-babel-load-file "/path/to/your/org-init-file.org") >> >> while users of lesser Emacs will have to load a new version of Org-mode >> before calling org-babel-load-file. > > Sorry, I have no idea how to update worg. > Don't worry, worg can tell you. http://orgmode.org/worg/#sec-4 > >> compiled and un-compiled code. If this does pose a problem for you, >> perhaps an optional extra argument to be added to org-babel-load-file to >> enable compilation. > > Yes, this would do nicely. > Done. > >> Great idea. I don't have time to work on this right now, but it is >> definitely on my stack. I suppose this should be the default behavior >> for all tangled files (not just those written by org-babel-load-file). > > Yes. Perhaps also include a comment that the file was tangled from an > org-file plus the path to that file. > Done, the chmod value should probably be made customizable through a new header argument at some point. As for a "tangled from X" comment, I'd rather not add extra comments to the code file by default, however there already exists a tangle option which may fill this need [1]. Cheers, Footnotes: [1] http://orgmode.org/manual/comments.html -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] babel perl issue
Bastien writes: > Achim Gratz writes: >> I hope you are not suggesting to put all of ob into a single file… > > Actually that's a good idea! Uh-oh… I'm not sure why you like that, but you'd then have the same problem inside that single file. It's solveable, but it means you'd need to put in lots of forward declarations or put things into a somewhat illogical order, which is surely detrimental for maintainability. You might want to ask Nicolas for his opinion, he's been having a lot of the same problems for the new exporter, for essentially the same reason. IIRC, it took some time to really sort out. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] babel perl issue
Eric Schulte writes: > In the absence of better ideas, I'm going to go ahead with this > refactoring. Okay, go ahead. But be warned that ob-core.el is not my friend :) I'll see how we can get rid of it. -- Bastien
Re: [O] Graphic of the Org-mode require structure
Eric Schulte writes: > This is a visualization of which Org-mode files require which other > Org-mode files. It may not hold any new insights, but I found it > interesting. There are a few false positives due to require forms in docstrings (org-latex.el seems to require itself for that reason) and maybe comments. But a great demonstration of how powerful Org-Babel really is! Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
[O] [new exporter] ASCII export, single newline
Hi all Trying out the new exporter... for my (very basic) purposes it is working fine - except one detail I can't find an answer to. I frequently have to make structured lists and email them to the office. I make each list as a table in an Org subtree, with some notes (always just plain text) above and below the table. At least for my purposes, the table export to ASCII works perfectly. My plain-text notes, however, often contain single newlines, which I'd like to retain. The new ASCII exporter converts them to spaces. If I put double newlines in the original, then the exporter doesn't convert anything, and leaves them double. I'm glad to format my originals in any way that works - my aim is only to get single newlines into the finished export. Is there an easy way to do that? -- Thanks David
Re: [O] babel perl issue
Bastien writes: > Eric Schulte writes: > >> In the absence of better ideas, I'm going to go ahead with this >> refactoring. > > Okay, go ahead. But be warned that ob-core.el is not my friend :) > :) > I'll see how we can get rid of it. If you can find a cleaner alternative I'll be happy to help you apply it. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte
[O] Bug: non-interactive org-export-region-as... modifies kill-ring [7.9.2 (release_7.9.2-103-g488eea)]
Title says it all. For example evaling (org-export-region-as-latex (point-min) (point-max) nil (get-buffer-create "res")) via M-: in an org-mode buffer will put the export content in the kill ring. That's not nice. I think only the interactive call should do that. Christopher
[O] correct spaces after colons with LaTeX
Hi LaTeX org-moders. I'm trying to get a non-sentence-ending space after a colon in LaTeX with org-mode. When I put a backslash after a colon to get the ordinary end-of-word space, org-mode changes it to "\backslash", which puts a backslash in the text. I also tried "\space", but that gave the large space. Similarly, ":~" was changed into ":\tilde". Is there some way I can escape my backslash so that org-mode will pass it to LaTeX as an actual backslash? Or is there another good way to get org-mode to tell LaTeX that I'm not ending a sentence with my colon? Thanks, David Moulton
Re: [O] correct spaces after colons with LaTeX
I found a reasonable solution: using ":\;" with no trailing space gives the right amount of space after the colon. David On Wed, 12 Dec 2012, David P. Moulton wrote: Hi LaTeX org-moders. I'm trying to get a non-sentence-ending space after a colon in LaTeX with org-mode. When I put a backslash after a colon to get the ordinary end-of-word space, org-mode changes it to "\backslash", which puts a backslash in the text. I also tried "\space", but that gave the large space. Similarly, ":~" was changed into ":\tilde". Is there some way I can escape my backslash so that org-mode will pass it to LaTeX as an actual backslash? Or is there another good way to get org-mode to tell LaTeX that I'm not ending a sentence with my colon? Thanks, David Moulton
Re: [O] bug#12905: 24.2.50; org: edit source block causes data loss
Hi Bastien, I'm not sure if this is related or not - I don't have time to track down the offending commit right now. org-edit-special (C-c ') is currently broken in master. I get the following backtrace --8<---cut here---start->8--- Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil) copy-marker(nil t) org-edit-src-code() org-edit-special() call-interactively(org-edit-special nil nil) --8<---cut here---end--->8--- GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-12-11 on raven, modified by Debian Org-mode version 7.9.2 (release_7.9.2-664-gb1f369 @ /home/bernt/git/org-mode/lisp/) Thanks, Bernt Bastien writes: > Hi Chong, > > Chong Yidong writes: > >> Could you please take a look at Bug#12905? If it causes data loss, I >> think it should be fixed in the emacs-24 branch. Thanks. > > This is fixed, thanks for the heads up. > > I just merged the Org bugfix branch into emacs-24. > > I made one mistake: I backported Paul's fixes about whitespaces in > our bugfix branch*, so those fixes are now in emacs-24 too, not in > the trunk only. I hope this won't create merge conflicts. > > * http://orgmode.org/cgit.cgi/org-mode.git/commit/?h=maint&id=e5ea08
Re: [O] org-drill installation problem
anybody there to rescue me ? :-| - *Sanjib Sikder *Ph.D. Fellow Chemical Engineering IIT Bombay* * On Tue, Dec 11, 2012 at 3:34 PM, Sanjib Sikder wrote: > hi, > > I downloaded the org-drill package and put the org-drill.el file > in.emacs.d folder. Then I added > > (require 'org-drill) > > in my .emacs file where the load path > > (add-to-list 'load-path "~/.emacs.d/") > > is there before it. > > After restarting, when i open a org-mode file to be used in org-drill > mode, it gives a warning : > > Warning (initialization): An error occurred while loading > `/home/ss/.emacs': > > File error: Cannot open load file, org-learn > > Also when I do > > M-x org-drill > > It cannot find org-drill > > I am using emacs-snapshot. What am I doing wrong ? > > Thanks. > - > *Sanjib Sikder > *Ph.D. Fellow > Chemical Engineering > IIT Bombay* > > * > >
Re: [O] org-capture vs. org-agenda-capture
As a matter of fact, when called from the agenda `%U' doesn't expand as the
current timestamp but rather provides the date of the line your point is on.
Wouldn't it be more convenient to get the current timestamp anyway?
Suppose you would like to create a new appointment then
1. you view your agenda to see whether you're free on a particular date
2. you place the cursor on that date line
3. you invoke org-agenda-capture (hit `k' key) from there
then a template such as this one
("a" "Appointment" entry (file+headline "~/gtd.org" "Inbox")
"* APPT %?\n %^T\n Added: %U")
would expand as
* APPT Dentist
<2012-12-25 Tue 18:00-19:00>
Added: [2012-12-12 Wed 22:13]
which makes sense; instead of
* APPT Dentist
<2012-12-25 Tue 18:00-19:00>
Added: [2012-12-25 Wed 00:00]
as it is today.
--
Rene
Re: [O] bug#12905: 24.2.50; org: edit source block causes data loss
On 12 December 2012 16:05, Bernt Hansen wrote: > Hi Bastien, > > I'm not sure if this is related or not - I don't have time to track down > the offending commit right now. > > org-edit-special (C-c ') is currently broken in master. > > I get the same thing when trying (C-c ') on the #+begin_src line. When trying it within the body of the source block it works properly > I get the following backtrace > > --8<---cut here---start->8--- > Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil) > copy-marker(nil t) > org-edit-src-code() > org-edit-special() > call-interactively(org-edit-special nil nil) > --8<---cut here---end--->8--- > > GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-12-11 > on raven, modified by Debian > > Org-mode version 7.9.2 (release_7.9.2-664-gb1f369 @ > /home/bernt/git/org-mode/lisp/) > > Thanks, > Bernt > > Regards, Jon > > Bastien writes: > > > Hi Chong, > > > > Chong Yidong writes: > > > >> Could you please take a look at Bug#12905? If it causes data loss, I > >> think it should be fixed in the emacs-24 branch. Thanks. > > > > This is fixed, thanks for the heads up. > > > > I just merged the Org bugfix branch into emacs-24. > > > > I made one mistake: I backported Paul's fixes about whitespaces in > > our bugfix branch*, so those fixes are now in emacs-24 too, not in > > the trunk only. I hope this won't create merge conflicts. > > > > * http://orgmode.org/cgit.cgi/org-mode.git/commit/?h=maint&id=e5ea08 > >
Re: [O] org-drill installation problem
Hello Sanjib, have subscribed to this mailing list.? (https://lists.gnu.org/mailman/listinfo/emacs-orgmode) Memnon Anon has replied to you with a solution. did you try that.? Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు YYR
Re: [O] bug#12905: 24.2.50; org: edit source block causes data loss
For me it occurs both inside the block (begin_src or begin_example) and on the first line. Regards, Bernt Jonathan Leech-Pepin writes: > On 12 December 2012 16:05, Bernt Hansen wrote: > > Hi Bastien, > > I'm not sure if this is related or not - I don't have time to track down > the offending commit right now. > > org-edit-special (C-c ') is currently broken in master. > > I get the same thing when trying (C-c ') on the #+begin_src line. When trying > it within the body of the source block it works properly > > I get the following backtrace > > --8<---cut here---start->8--- > Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p > nil) > copy-marker(nil t) > org-edit-src-code() > org-edit-special() > call-interactively(org-edit-special nil nil) > --8<---cut here---end--->8--- > > GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-12-11 > on raven, modified by Debian > > Org-mode version 7.9.2 (release_7.9.2-664-gb1f369 @ > /home/bernt/git/org-mode/lisp/) > > Thanks, > Bernt > > Regards, > Jon > > Bastien writes: > > > Hi Chong, > > > > Chong Yidong writes: > > > >> Could you please take a look at Bug#12905? If it causes data loss, I > >> think it should be fixed in the emacs-24 branch. Thanks. > > > > This is fixed, thanks for the heads up. > > > > I just merged the Org bugfix branch into emacs-24. > > > > I made one mistake: I backported Paul's fixes about whitespaces in > > our bugfix branch*, so those fixes are now in emacs-24 too, not in > > the trunk only. I hope this won't create merge conflicts. > > > > * http://orgmode.org/cgit.cgi/org-mode.git/commit/?h=maint&id=e5ea08
Re: [O] [new exporter] ASCII export, single newline
Hello, David Rogers writes: > My plain-text notes, however, often contain single newlines, which I'd > like to retain. The new ASCII exporter converts them to spaces. If I put > double newlines in the original, then the exporter doesn't convert > anything, and leaves them double. I'm glad to format my originals in any > way that works - my aim is only to get single newlines into the finished > export. Is there an easy way to do that? IIUC, you want line breaks. I.e: Some line \\ Some other line. If you want a line break on every line, use #+OPTIONS: \n:t Regards, -- Nicolas Goaziou
Re: [O] bug#12905: 24.2.50; org: edit source block causes data loss
Hi Bernt, Bernt Hansen writes: > I'm not sure if this is related or not - I don't have time to track down > the offending commit right now. There is nothing new regarding editing source code in master, except Eric's last few patches. > org-edit-special (C-c ') is currently broken in master. > > I get the following backtrace Mhh.. I can't reproduce this. > Org-mode version 7.9.2 (release_7.9.2-664-gb1f369 @ > /home/bernt/git/org-mode/lisp/) I'm on release_7.9.2-692-g627d57 ^^^ Are you sure you are using master HEAD? Thanks, -- Bastien
Re: [O] [new exporter] ASCII export, single newline
Nicolas Goaziou writes: > Hello, > > David Rogers writes: > >> My plain-text notes, however, often contain single newlines, which I'd >> like to retain. The new ASCII exporter converts them to spaces. If I put >> double newlines in the original, then the exporter doesn't convert >> anything, and leaves them double. I'm glad to format my originals in any >> way that works - my aim is only to get single newlines into the finished >> export. Is there an easy way to do that? > > IIUC, you want line breaks. I.e: > > Some line \\ > Some other line. Thanks... This is giving me two line breaks (i.e. inserting an unwanted blank line into the result). I want one line break, but no blank line. > > If you want a line break on every line, use #+OPTIONS: \n:t Haven't tried this yet. -- Thanks David
Re: [O] org-capture vs. org-agenda-capture
Dear Rene,
Rene writes:
> As a matter of fact, when called from the agenda `%U' doesn't expand as the
> current timestamp but rather provides the date of the line your point is on.
Depends. From the agenda, you can use either org-capture directly, or
org-agenda-capture. org-capture will convert %U using current time, not
the time of the agenda line -- unless `org-capture-use-agenda-date' is t.
> Wouldn't it be more convenient to get the current timestamp anyway?
If you want the date the cursor is on, I think 00:00 as a default time
makes sense, mixing the current time and the date line would be confusing
IMHO.
> Suppose you would like to create a new appointment then
> 1. you view your agenda to see whether you're free on a particular date
> 2. you place the cursor on that date line
> 3. you invoke org-agenda-capture (hit `k' key) from there
>
> then a template such as this one
>
> ("a" "Appointment" entry (file+headline "~/gtd.org" "Inbox")
>"* APPT %?\n %^T\n Added: %U")
>
> would expand as
>
> * APPT Dentist
> <2012-12-25 Tue 18:00-19:00>
> Added: [2012-12-12 Wed 22:13]
>
> which makes sense; instead of
>
> * APPT Dentist
> <2012-12-25 Tue 18:00-19:00>
> Added: [2012-12-25 Wed 00:00]
>
> as it is today.
I guess M-x org-capture is enough here.
Best,
--
Bastien
Re: [O] Bug: non-interactive org-export-region-as... modifies kill-ring [7.9.2 (release_7.9.2-103-g488eea)]
Hi Christopher, Christopher Schmidt writes: > Title says it all. For example evaling (org-export-region-as-latex > (point-min) (point-max) nil (get-buffer-create "res")) via M-: in an > org-mode buffer will put the export content in the kill ring. That's > not nice. I think only the interactive call should do that. There is org-export-copy-to-kill-ring. I added a new choice 'if-interactive which is now the default: exported text will only be pushed to the kill ring when export is done interactively. You can always set it to nil if you want. Best, -- Bastien
Re: [O] org-bullets extension
Hi Evgeni, E Sabof writes: > I am the author of org-bullets extension, which can be found at > github.com/sabof/org-bullets This is very nice, we have so many requests about changing the "*" character that I guess people will love this. > I wondered whether you would like to include it in org-contrib, or > perhaps integrate the functionality in org-mode? I would like to include this in contrib. Can you license it under GPLv3 and make all the related cosmetic changes? Also, if you can, don't require 'cl at run time... Use (eval-when-compile (require 'cl)) instead. And the defun* can simply be defun from what I've seen. Thanks in any case for sharing this! -- Bastien
Re: [O] The statement on what is orgmode.
> Org-mode is useful for > > - Organising projects, maintaining TODO lists and calendars > > - Creating high quality formatted documents > > - Keeping notes > > - Literate programming and Reproducible Research > > > > After a rather fruitful discussion, this thread has gone dead before power-that-be would take note. Who is responsible for making changes on the orgmode website? Vikas
Re: [O] The statement on what is orgmode.
Vikas Rawal writes: > After a rather fruitful discussion, this thread has gone dead before > power-that-be would take note. Who is responsible for making changes > on the orgmode website? Until someone volonteers to maintain the website, I am in charge. Can you summarize the change we need to make? If not, I will process this when I have some time. Thanks, -- Bastien
Re: [O] The statement on what is orgmode.
Hi Vikas, Vikas Rawal writes: > And the first headline, before "Download and install", be something > like the following: > > * Org mode is useful for > ** Organising projects > ** Maintaining TODO lists and calendars > ** Keeping notes > ** Creating high quality formatted documents > ** Literate programming > > Each of the above could then be linked to relevant pages of the manual > or worg. Be careful not to be redundant with the list of features here: http://orgmode.org/features.html What I would love is to have some videos instead of the pictures on the features page. Anyone? Also, orgweb.git is publicly accessible here: git://orgmode.org/orgweb.git Patch welcome! -- Bastien
Re: [O] The statement on what is orgmode.
Jambunathan K writes: > ps: I have org-e-freemind.el based on new exporter almost done. It just > requires some tweaking before it lands. Great news hidden in this threads! Looking forward to testing this, -- Bastien
Re: [O] The statement on what is orgmode.
7. Org-mode: don't tell your boss. Vikas Rawal writes: > 1. Org-mode (only) > 2. Org-mode: your life in plain text > 3. "Orgmode is a Free/libre plain-text system for GNU Emacs for > organizing project, and maintaining TODO lists, keeping notes, doing > literate programming and exporting to many high quality formats." > 4. Orgmode is a Free/libre plain-text versatile personal workflow and > information tool for GNU Emacs allowing you to keep and organize > notes, projects, calendars, do literate programming and reproducible > research, and export all your informations and documents to a variety > of cam-ready formats. > 5. Org-mode: the text editor's best chance at achieving the singularity. > 6. Org-mode: It's difficult to say what exactly Emacs' Org-mode will > do for you; it's easier to list all things it doesn't do. -- Bastien
Re: [O] org-gnome-calendar
Hi Lluís, Lluís Vilanova writes: > It's just barely working and quite slow, but here's an initial tentative on a > package to get the agenda in Org mode to show up in GNOME's calendar: > > https://github.com/llvilanova/org-gnome-calendar Looks interesting. Any screenshots/videos for those of use who don't use Gnome? Thanks! -- Bastien
Re: [O] org-sync doesn't work with recent org-element.el
Hi all, On Wed, Dec 12, 2012 at 3:42 PM, Bastien wrote: > I'm copying Aurélien, the author of org-sync. I saw the thread but thank you anyway. > Aurélien, are you willing to maintain org-sync or shall we call for > a new maintainer? I have not given up on org-sync but I have too many things going on right now. I know it's not the first time I say this but I will get back to it eventually.
Re: [O] bug#12905: 24.2.50; org: edit source block causes data loss
Bastien writes: > Hi Bernt, > > Bernt Hansen writes: > >> I'm not sure if this is related or not - I don't have time to track down >> the offending commit right now. > > There is nothing new regarding editing source code in master, > except Eric's last few patches. > >> org-edit-special (C-c ') is currently broken in master. >> >> I get the following backtrace > > Mhh.. I can't reproduce this. > >> Org-mode version 7.9.2 (release_7.9.2-664-gb1f369 @ >> /home/bernt/git/org-mode/lisp/) > > I'm on release_7.9.2-692-g627d57 > ^^^ > > Are you sure you are using master HEAD? I think so. I just updated and have the same behaviour Org-mode version 7.9.2 (release_7.9.2-693-g8c04fb @ /home/bernt/git/org-mode/lisp/) I'll try and locate the problem commit. Regards, Bernt
Re: [O] bug#12905: 24.2.50; org: edit source block causes data loss
Bernt Hansen writes: > Bastien writes: > >> Hi Bernt, >> >> Bernt Hansen writes: >> >>> I'm not sure if this is related or not - I don't have time to track down >>> the offending commit right now. >> >> There is nothing new regarding editing source code in master, >> except Eric's last few patches. >> >>> org-edit-special (C-c ') is currently broken in master. >>> >>> I get the following backtrace >> >> Mhh.. I can't reproduce this. >> >>> Org-mode version 7.9.2 (release_7.9.2-664-gb1f369 @ >>> /home/bernt/git/org-mode/lisp/) >> >> I'm on release_7.9.2-692-g627d57 >> ^^^ >> >> Are you sure you are using master HEAD? > > I think so. I just updated and have the same behaviour > > Org-mode version 7.9.2 (release_7.9.2-693-g8c04fb @ > /home/bernt/git/org-mode/lisp/) > > I'll try and locate the problem commit. git bisect identifies the following commit: --8<---cut here---start->8--- 206257aa7eb83a0a62f297e7cf0e3a7c32ff6f05 is the first bad commit commit 206257aa7eb83a0a62f297e7cf0e3a7c32ff6f05 Author: Le Wang Date: Sun Nov 18 13:39:51 2012 +0800 org-src: Fix org-edit-src-code for empty blocks and block with just an empty line * lisp/org-src.el (org-edit-src-code): Use marker with insertion type t to track end and remove hack requiring delete from beg to (1- end). :04 04 91825ba365592800804e652e3ad66db0f8302772 25f089bf9456b306afd2a0e538bcbfefc4a124f0 M lisp --8<---cut here---end--->8--- I'm just trying to edit a lisp source block --8<---cut here---start->8--- * test [2012-12-09 Sun 20:53] #+begin_src lisp (defun bh/show-org-agenda () (interactive) (switch-to-buffer "*Org Agenda*") (delete-other-windows)) ; Use the current window for C-c ' source editing (setq org-src-window-setup 'current-window) #+end_src --8<---cut here---end--->8--- using C-c ' inside the block. Reverting this commit fixes it for me. Regards, Bernt
Re: [O] bug#12905: 24.2.50; org: edit source block causes data loss
Bernt Hansen wrote: > Bernt Hansen writes: > > > Bastien writes: > > > >> Hi Bernt, > >> > >> Bernt Hansen writes: > >> > >>> I'm not sure if this is related or not - I don't have time to track down > >>> the offending commit right now. > >> > >> There is nothing new regarding editing source code in master, > >> except Eric's last few patches. > >> > >>> org-edit-special (C-c ') is currently broken in master. > >>> > >>> I get the following backtrace > >> > >> Mhh.. I can't reproduce this. > >> > >>> Org-mode version 7.9.2 (release_7.9.2-664-gb1f369 @ > >>> /home/bernt/git/org-mode/lisp/) > >> > >> I'm on release_7.9.2-692-g627d57 > >> ^^^ > >> > >> Are you sure you are using master HEAD? > > > > I think so. I just updated and have the same behaviour > > > > Org-mode version 7.9.2 (release_7.9.2-693-g8c04fb @ > > /home/bernt/git/org-mode/lisp/) > > > > I'll try and locate the problem commit. > > git bisect identifies the following commit: > > 206257aa7eb83a0a62f297e7cf0e3a7c32ff6f05 is the first bad commit > commit 206257aa7eb83a0a62f297e7cf0e3a7c32ff6f05 > Author: Le Wang > Date: Sun Nov 18 13:39:51 2012 +0800 > > org-src: Fix org-edit-src-code for empty blocks and block with just an > empty line > > * lisp/org-src.el (org-edit-src-code): Use marker with insertion type > t to track end and remove hack requiring delete from beg to (1- end). > > :04 04 91825ba365592800804e652e3ad66db0f8302772 > 25f089bf9456b306afd2a0e538bcbfefc4a124f0 Mlisp > > I'm just trying to edit a lisp source block > > * test > [2012-12-09 Sun 20:53] > > #+begin_src lisp > (defun bh/show-org-agenda () > (interactive) > (switch-to-buffer "*Org Agenda*") > (delete-other-windows)) > > ; Use the current window for C-c ' source editing > (setq org-src-window-setup 'current-window) > > #+end_src > > using C-c ' inside the block. > > Reverting this commit fixes it for me. > FWIW, I cannot reproduce this and I do have the commit you fingered in my tree. Could it be the emacs version that makes a difference here? Mine is GNU Emacs 24.2.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.4) of 2012-09-21 Nick
Re: [O] [new exporter] ASCII export, single newline
Nicolas Goaziou writes: > Hello, > > David Rogers writes: > >> My plain-text notes, however, often contain single newlines, which I'd >> like to retain. The new ASCII exporter converts them to spaces. If I put >> double newlines in the original, then the exporter doesn't convert >> anything, and leaves them double. I'm glad to format my originals in any >> way that works - my aim is only to get single newlines into the finished >> export. Is there an easy way to do that? > > IIUC, you want line breaks. I.e: > > Some line \\ > Some other line. Exporting the double backslash adds an extra blank line, which I don't want. > If you want a line break on every line, use #+OPTIONS: \n:t This gave me exactly what I was looking for, thank you. My line breaks are preserved, but no new ones are added. (The old ASCII exporter preserved line breaks, without using any OPTIONS.) -- David
