On Sun, Nov 6, 2011 at 1:59 PM, Pieter Praet wrote:
> On Sat, 5 Nov 2011 16:35:11 -0700, Samuel Wales wrote:
>> I used to find that 8-bit 75dpi was legible and small.
>>
>
> True.
>
> It all depends on why you're scanning them in the first place.
>
> 75dpi is fine when scanning with collaboration
On Thu, 3 Nov 2011 23:26:57 + (UTC), Herbert Sitz wrote:
> Michael -- No problem, this issue was of course brought up when I
> started the project a year or so ago. Actually for the many Vim users
> who have tried to make the transition to Emacs I think it is pretty
> well known that there ar
David Maus wrote:
> > What a mess - thanks for the clear explanation. Be that as it may, the
> > treatment of links in org-insert-link is inconsistent: in one case, the
> > link is unescaped once, in the other not at all.
>
> Hm. I still don't see an inconsistency here: `org-insert-link' reads a
Markus Grebenstein mgrebenstein.de> writes:
>
> since I used Scrivener (Windows Beta) quite a while I'd love to have
> more of fletcher penny's multimarkdown (or MMD- like Syntax) integrated
> in orgmode to make it more versatile. Sadly I am not a lisp programmer
> at all...
>
Markus --
Wha
On Sat, 5 Nov 2011 16:35:11 -0700, Samuel Wales wrote:
> I used to find that 8-bit 75dpi was legible and small.
>
True.
It all depends on why you're scanning them in the first place.
75dpi is fine when scanning with collaboration/quick-reference in mind,
but for archival/backup purposes (i.e.
> I tried and it is not necessary to org-reload/uncompiled before
> installing org with the command "package-install-file". It is
> "package-install-file" alone that solves the problem.
Maybe there is some aspect of elisp compilation that I don't
understand.
1. Restart Emacs
2. If M-x locate-l
Am 06.11.2011 um 22:01 schrieb Jambunathan K:
> "i...@bastianebeling.org" writes:
>
>> Hi Jambunathan,
>>
>>>
Sorry, I didn't get into too much detail here because I had the
feeling that the problem might have been cause by me not being able
to use the package manager correctly
"i...@bastianebeling.org" writes:
> Hi Jambunathan,
>
>>
>>> Sorry, I didn't get into too much detail here because I had the
>>> feeling that the problem might have been cause by me not being able
>>> to use the package manager correctly rather than the package manager
>>> itself. But if it coul
here is a patch implementing category filtering in the agenda.
The patch is not 100% clean wrt documentation, but I throw it
now to get some feedback and some testing done.
Press "<" in the agenda to filter by category.
Press "< <" to filter by the category of the entry point.
Another "/ /"
1. C-h i
2. m org
3. i visibility
4. keep pressing "," until you land up where all visibility is
documented.
1 => launch info
2 => visit org manual
3 => index lookup for visibility
4 => cycle through all entries
> Okay, I figured it out. There's a visibility property for that, e.g.:
>
> :PRO
Achim Gratz writes:
> Jambunathan K writes:
>> FYI, if Org is insalled through the package manager there is no
>> org-install.el. Package manager creates autoloads on it's own and names
>> it org-autoloads.el.
>>
>> I believe, for most part, org-install and org-autoloads have the same
>> functio
Okay, I figured it out. There's a visibility property for that, e.g.:
:PROPERTIES:
:VISIBILITY: content
:END:
Cheers,
Marius
On 2011-11-06, at 15:27 , Marius Hofert wrote:
> Hi,
>
> as described on http://orgmode.org/manual/Visibility-cycling.html one can set
> #+STARTUP: content to start an
Jambunathan K writes:
> FYI, if Org is insalled through the package manager there is no
> org-install.el. Package manager creates autoloads on it's own and names
> it org-autoloads.el.
>
> I believe, for most part, org-install and org-autoloads have the same
> functionality.
Then maybe they shoul
FYI, if Org is insalled through the package manager there is no
org-install.el. Package manager creates autoloads on it's own and names
it org-autoloads.el.
I believe, for most part, org-install and org-autoloads have the same
functionality.
> Recent changes in my Makefile fork:
>
> org-version
Recent changes in my Makefile fork:
org-version has been changed to always get the version information from
org-install.el. This way, there is no need to invoke a shell in
org-version or to keep any version information in org.el. Additionally
org-version checks where it finds org-install.el and
Bastien writes:
> Press "< <" to filter by the category of the entry point.
... "of the entry AT point" ... of course.
--
Bastien
Dear all,
here is a patch implementing category filtering in the agenda.
The patch is not 100% clean wrt documentation, but I throw it
now to get some feedback and some testing done.
Press "<" in the agenda to filter by category.
Press "< <" to filter by the category of the entry point.
Anot
Dear org-mode community,
I am configuring my LaTeX export setup and found LaTeX src blocks very
nice for the font lock they provide and the possibility of having AUCTeX
activated for that block by =C-c '=. However, org's LaTeX exporter puts
them into a \verbatim environment by default in the resu
At Thu, 03 Nov 2011 19:35:01 -0200,
Cassio Koshikumo wrote:
>
> Hi, all,
>
> On the last few days I've been working on a major mode derived from org-mode.
> While I was at it, I've encoutered some difficulties related to those reported
> by the OP (Stefan). Specifically: in a lot of places, org-mod
Running the test suit on
GNU Emacs 22.3.2 (i686-pc-linux-gnu) of 2011-05-28 on x60s
currently fails with the backtrace below.
Somehwere/somehow Babel ends up calling `member' with the second
argument not being a list. In Emacs22 this triggers an error, but not
so in Emacs23 and upwards.
Devs do
At Sat, 05 Nov 2011 11:38:56 -0400,
Nick Dokos wrote:
>
> David Maus wrote:
>
> > At Fri, 04 Nov 2011 14:25:42 -0400,
> > Nick Dokos wrote:
> > >
> > > Nick Dokos wrote:
> > >
> > > > It probably does, but that's probably not the best place to do it: it
> > > > might be
> > > > better to do it i
Hi,
as described on http://orgmode.org/manual/Visibility-cycling.html one can set
#+STARTUP: content to start an .org file with all headlines shown, the default
is "overview". I tried to put "#+STARTUP: content" in some sections hoping that
they will be expanded on startup while other sections
Hello,
Markus Grebenstein writes:
> If of any interest I can try to reproduce this in a less than 9500
> word ducument.
Yes, I would appreciate an ECM (minimal complete example) along with the
version of Org you're using.
Thank you.
Regards,
--
Nicolas Goaziou
Dear community,
since I used Scrivener (Windows Beta) quite a while I'd love to have
more of fletcher penny's multimarkdown (or MMD- like Syntax) integrated
in orgmode to make it more versatile. Sadly I am not a lisp programmer
at all...
Best Markus
Dear Orgmode community,
last week I submitted a journal paper of appr. 30 pages using orgmode
and latex export and I ran into trouble regarding footnotes several times.
The document didn't compile due to wrongly set brackets of footnotes if:
A footnote is placed without a blank line infront of
How can I set up anniversaries with org-contact?
My agend.org file contains the following, as mentioned on the bottom of
http://julien.danjou.info/org-contacts.html
#+STARTUP: showeverything
* Birthdays
%%(org-contacts-anniversaries)
My contacts.org file contains (e.g.):
* My contact
Hi,
I would like to capture contacts (name, email,..) with org-mode and thus setup
the following in .emacs:
(setq org-capture-templates
'(("t" "TODO in ~/org/agenda.org -> Tasks" entry (file+headline
"~/org/agenda.org" "Tasks")
"* TODO %?\nSCHEDULED: %^t\n%U %a")
("c" "Co
Thanks a lot, Jan, that explained it very well.
Cheers,
Marius
On 2011-11-06, at 11:30 , Jan Böcker wrote:
> On 11/05/2011 11:35 PM, Marius Hofert wrote:
>
>> Apparently, the string "SCHEDULED:" is not required for an entry to appear
>> in agenda view.
>
> Hi Marius,
>
> the difference bet
On 11/05/2011 11:35 PM, Marius Hofert wrote:
> Apparently, the string "SCHEDULED:" is not required for an entry to appear in
> agenda view.
Hi Marius,
the difference between and SCHEDULED: is that will
cause the entry to appear in the agenda only on the given day, whereas
SCHEDULED: will a
29 matches
Mail list logo
