Re: [O] inserting a path string fires the italic formatting
Sebastien Vauban writes: Hi Luca, Luca Ferrari wrote: this could be trivial, but if I have to place a unix path name into my org text, without having a link, how can I prevent the mode to assume I'm doing italic formatiing? For instance in the text: - check /usr/bin/chmod - check /usr/lib/bla Suggestions? For example, by protecting those paths, declaring them as `org-code' or `org-verbatim', that is using the markers `=' or `~'; for example: - check ~/usr/bin/chmod~ - check ~/usr/bin/bla~ Looks like Emacs backup files somewhere in a user's home directory ;-) -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
Re: [O] Language for agenda
Bastien writes: twiki twiki7...@yahoo.it writes: How can you change the language in which Emacs displays the Agenda in Org-mode? (setq calendar-day-name-array [lunedì martedì mercoledì giovedì venerdì sabato domenica]) (setq calendar-month-name-array [gennaio febbraio marzo aprile maggio giugno luglio agosto settembre ottobre novembre dicembre]) (setq-default system-time-locale it) or similar ought to do the trick as well. As would starting emacs with your locale set to Italian. Something like LANG=it_IT.UTF8 emacs Hope this helps -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
Re: [O] Problem with exporting TAB key
Vladimir Lomov lomov...@gmail.com writes: Hello, ** Nick Dokos [2012-04-05 00:13:10 -0400]: Vladimir Lomov lomov...@gmail.com wrote: #+TITLE: Problem with exporting TAB key #+AUTHOR: Vladimir Lomov * How to make TAB key to be exported from ORG document? Consider the following example: #+name: ex1 #+BEGIN_SRC sh :exports code sort -t -k 3 -o file2 file1 sort -t -k 3 -o file3 file #+END_SRC How I inserting the TAB key in example: for first line I use =C-q C-I=, for second line I use =C-q TAB=, but in tangled file and in exported HTML document it is NOT a TAB just spaces. Just a thought but can't you use \t? -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
Re: [O] Temp files from testing are permanent...
FTR, I'm just commenting based on experience with a testing harness for a completely unrelated piece of software. Achim Gratz strom...@nexgo.de writes: Eric Schulte eric.schu...@gmx.com writes: I should have been more clear. I'm thinking that this would be a macro used /within/ unit tests so that testers could specify what files will be created (test writers should be able to predict the file names created by their tests) and then the macro will handle cleanup. Test writers can predict/choose the file names created by their tests but they cannot predict the file names creates by other test writers' tests (or their own tests written two weeks ago ;-). Unless there is some naming policy that is strictly adhered to, the chance of collisions remains. One approach that has worked for me is to have tests create their outputs in a directory named after the test. So if I have a test implemented in test.el, it would create all outputs in test.out/, for example. As I put all my tests and their inputs in a tests/ directory (and nothing else), I can just `rm -rf *.out` there to clean up. I'm sitting on the fence with this. Running the tests from the Makefile it would probably be more difficult to ensure that one could keep the files when the tests were trying to clean up after themselves (as some option would need to be injected into the test invocation and/or a different test command would need to be called). Personally, I prefer to have `make clean` take care of cleaning up my test outputs. I control when it gets run, can move valuable stuff out of the way before doing so and none of the tests have to bother with conditionalized clean up. I do like the idea of a single directory in which all output files may be collected. The only potential downside I see for this is that files will be generated both from within org files in the testing/examples directory as well as temporary files. The temporary files could be in a sub-directory... or each test (group) could have their own sub-directory. Whatever the organisation, there should be a single directory which, if recursively removed, gets rid of all files created by the test run. See above. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
Re: [O] Temp files from testing are permanent...
Achim Gratz strom...@nexgo.de writes: Olaf Meeuwissen olaf.meeuwis...@avasys.jp writes: If running `make check` (or similar) creates these files, `make clean` (or similar) should clean them up. I was asking that question to decide whether I do need to extend my Makefile fork to handle the cleanup or if the testsuite needs to be called differently to avoid leaving these stale files. If you'd take a look, you can see that the files are obviously made with a function that ensures they're unique, most likely make-temp-file. If so, it would seem logical that the testsuite should remove them after each test (since it is the only instance to know the complete filename). It would also seem logical that for debugging purposes one could leave the files around. Successful tests can clean up after themselves but failed tests should not so you can debug. The decision to remove these files should be left to whoever runs the test suite. That implies that even successful tests don't really have to bother cleaning up after themselves. I normally instruct my tests to create files in a dedicated directory with a fixed name somewhere below $(top_builddir). Then a `make clean` can just remove the whole directory. If you use `make check` to run the test suite, you can easily set TMPDIR via the TESTS_ENVIRONMENT Makefile variable (assuming that that variable is taken into account when making unique file names). Something like TESTS_ENVIRONMENT = TMPDIR=$(builddir)/test-outputs and then add a clean-local target like clean-local: -rm -rf $(builddir)/test-outputs See [[info:automake-1.11#Simple%20Tests][info:automake-1.11#Simple Tests]] and [[info:automake-1.11#Extending]] for details. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
Re: [O] Temp files from testing are permanent...
Achim Gratz strom...@nexgo.de writes: I've started to always test each build. It seems that the temporary files from testing (they end up in /tmp) are not actually removed after testing and continue to pile up. Is there an option that I might have missed that prevents these files from being removed or should cleaning those files be added to the Makefile? Im starting the test suite with If running `make check` (or similar) creates these files, `make clean` (or similar) should clean them up. See [[info:automake-1.11#Clean]] for details. /usr/local/bin/emacs -batch -u myself -L lisp/ \ --eval '(defconst org-release 7.8.03-Test)' \ -l testing/org-test.el \ -eval (setq org-confirm-babel-evaluate nil) \ -f org-test-run-batch-tests Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
Re: [O] Problem compiling C++ in Org-mode
Michael Hannon jm_han...@yahoo.com writes: Greetings. I'm having a problem compiling a C++ source-code block in Org-mode. The same C++ code compiles and runs in the shell. The issue seems to relate to local include files. [...snip...] What am I missing? /tmp/babel-245846_d/C-src-24584NIQ.cpp:7:26: fatal error: OtherStuff.cpp: No such file or directory compilation terminated. /bin/bash: /tmp/babel-245846_d/C-bin-24584aSW: Permission denied Compilation is taking place in a temporary directory, miles away from where your org file lives. ## Org-mode compile uses same option as shell compile: org-babel-C++-compiler is a variable defined in `ob-C.el'. Its value is g++ -std=c++0x The current directory is not specified in the include path. You would need to add a -I option to set the (absolute path to the) directory the org file is in. If you have all your org files in ~/org, you could try g++ -std=c++0x -I~/org. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
Re: [O] Suddenly, my timestamps get localized!
Sebastien Vauban wxhgmqzgw...@spammotel.com writes: Hi Tassilo, Tassilo Horn wrote: when I insert a new timestame, I now get 2011-10-25 Di while it used to be 2011-10-25 Tue until very recently. (Di is Dienstag which is German for Tuesday). I've briefly grepped the org source code, but I cannot see any localization there. What's going on? I even have no glue how org/emacs (correctly) guesses that I'm German. My locale is en_US.UTF-8... Found in my .emacs: #+begin_src emacs-lisp ;; system locale to use for formatting time values (e.g., timestamps in ;; Org mode files) (setq system-time-locale C) ;; en_US.utf8 did not work for the weekday in the agenda! #+end_src Now, the question is: why did it change on your machine? New Emacs, new Cygwin (if on Windows)? See discussion http://cygwin.com/ml/cygwin/2011-09/msg6.html on Cygwin (though I don't know what to understand from it...). Or updated localisation catalogs. I've also put (setq system-time-locale C) in my .emacs-en because that is the only sane settings if you move your org-files between accounts in any kind of way. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
Re: [O] why was makefile changed to produce this?
Jude DaShiell jdash...@shellworld.net writes: For the record, this is a new installation of debian wheezy and the makeinfo utility doesn't appear to be in the distribution let alone on my system. sudo apt-get install texinfo I usually keep a (somewhat stale) copy of Contents-$arch.gz around and find necessary packages with zegrep bin/makeinfo Contents-$arch.gz There is (was?) a package that would make package suggestions if a command isn't found but I can't recall its name. # Somewhat annoying when you make a typo but ... Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
Re: [O] why was makefile changed to produce this?
Nick Dokos nicholas.do...@hp.com writes: Jude DaShiell jdash...@shellworld.net wrote: My bad, I was missing texinfo package and thought that had already been installed. Once that got installed, everything works as well as it did earlier this year. If I knew what path that error took, I'd write what might be a better error message for it asking for the texinfo package to be installed. Here is a useful command that you can use on Debian and Ubuntu systems in situations like this: $ dpkg -S makeinfo texinfo: /usr/bin/makeinfo octave3.2-common: /usr/share/octave/3.2.4/m/help/__makeinfo__.m emacs23-common: /usr/share/emacs/23.1/lisp/textmodes/makeinfo.elc texinfo: /usr/share/man/man1/makeinfo.1.gz This only works for installed packages, though, as it searches the files below /var/lib/dpkg/info, IIRC. BTW, dpkg forwards that request to dpkg-query. [...] $ goo The program 'goo' is currently not installed. To run 'goo' please ask your administrator to install the package 'goo' In which case `apt-cache show goo` may be of help. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
[O] Storing log notes at capture (was Re: feature request for org-store-log-note)
John J Foerch jjfoe...@earthlink.net writes: I use org to manage TODO lists in which I want to keep time stamps for the creation of an item, and for each state change. To be as clear as possible, I'll just paste the portion of my config that affects how TODOs work: (setq org-treat-insert-todo-heading-as-state-change t org-log-into-drawer t org-log-done nil) ;;; [snip] (setcdr (assq 'state org-log-note-headings) State - %s %t) This logs each state change (including creation) into the LOGBOOK drawer. It's great. I thought so too. I'd like to record creation in the logbook drawer when I capture a TODO and have adjusted my templates to do so. They just include the logbook drawer literally, like so * TODO %? :LOGBOOK: - State \TODO\ from \\ %U :END: %a %i I thought that org-treat-insert-todo-heading-as-state-change would be able to create the drawer for me but no such luck. Duh, capturing is not a state change now is it. Anyway, is there a smarter way to log creation at capture? Thanks in advance, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
