Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?

2017-09-20 Thread Loris Bennett
Hi Tim,

Tim Cross  writes:

> Management of an emacs init file is a challenge for anyone who has been
> using Emacs for a long time. I did this after being a user for over 20
> years and like you, was a little daunted by the task. However, I now
> realise it was the single best thing I ever did to improve my emacs. I
> also had let my config grow organically and what I found out when I
> decided to clean it up was that a lot of what I had in there was
> unnecessary, was slowing down my Emacs (both startup and runtime) and
> that many of my long-term emacs 'annoyances' were actually due to
> incorrect or outdated settings in my init file.
>
> A few things I learned which may be of help
>
> 1. Put your init in git (or your favourite source control system ) and
> do your changes incrementally. You will need to revert to previous
> versions, so be methodical with checking in changes and do it
> incrementally.
>
> 2. Have a look at the use-package macro. This really cleaned up my init
> file, helped me make it more modular and really improved both the
> structure and maintenance as well as startup times etc.
>
> 3. I now use org to manage my init file. In fact, I have a few init
> files. I have a bare bones minimal init file which I use when I need to
> debug a specific feature/package or generate bug reports, I have an
> experimental one where I play with new things and I have my stable
> one. Using org, I can just 'tangle' a new init based on one of those
> files whenever I need it. I started by just putting all my existing
> setup into a block in an org file and exporting that as elisp. As time
> permitted, I broke bits off into their own blocks with explanatory
> comments/text so that I can remember why/what of the block.
>
> 4. Finally, there are some really good 'canned' configurations out
> there. I personally quite like purcell's setup (on github). While I
> don't use any of these per se, I did 'borrow' some of the ideas.
>
> My setup is now healthier and more stable than it ever has been. The
> effort is definitely worth it.
>
> Tim

[snip (28 lines)]

OK, you've convinced me - I'm sure you are right about potential
incorrect and outdated stuff.  I already have my .emacs in Git, so
that's a start and  I'll definitely have a look at 'use-package'.  I
might even go wild and move to init.el ;-)

Cheers,

Loris

--
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin Email loris.benn...@fu-berlin.de




Re: [O] Add ability to force-enable TOC

2017-09-20 Thread Carsten Dominik
On Tue, Sep 19, 2017 at 9:27 PM, Nicolas Goaziou 
wrote:

> Hello,
>
> Carsten Dominik  writes:
>
> > On Tue, Sep 19, 2017 at 4:49 PM, Kaushal Modi 
> > wrote:
> >
> >> Hello,
> >>
> >> I have use-cases where I don't like to see the headings numbered but
> still
> >> want the TOC to be generated.
> >>
> >> I have this in many of my Org files:
> >>
> >> #+OPTIONS: num:nil H:4
> >>
> >> But after commit bd23781[1], that has stopped working i.e. no TOC is
> >> created because of num:nil.
> >>
> >
> > I would see this as a bug - clearly it makes sense to have a TOC without
> > numbering.
> >
> > Nicolas, was this an oversight, or was this change intended?
>
> The change was intended. The idea was discussed on the ML. You may want
> to check the thread.
>
> This is on par with, e.g., what LaTeX does.
>

That may be so, but I find that unfortunate.  I am really using this
feature often.

I will go back and take a look at this thread.  Can someone tell me what
the subject line of that thread was?

Carsten


>
> Regards,
>
> --
> Nicolas Goaziou
>


Re: [O] Add ability to force-enable TOC

2017-09-20 Thread Nicolas Goaziou
Hello,

Kaushal Modi  writes:

> On Tue, Sep 19, 2017 at 3:57 PM Nicolas Goaziou 
> wrote:
>
>> What is exactly the feature you are missing? Your example is a special
>> case where _no_ heading is numbered.
>
>
> I would not consider this as a special case. It is very common for HTML
> exports to not always number the headings.

I didn't say it was an unusual case. I said it didn't cover all the
use-cases. Maybe you are really needing a subset of the initial feature.
IOW, do mixed numbered/unnumbered headings make sense in TOC?

>> 1. it makes all export back-ends consistent with TOC;
>>
>
>  I understand that. But would like a way to get back the earlier behavior
> too.

Then there is the other way around: how do we tell LaTeX to include both
numbered and unnumbered headings?

And: how do we distinguish @unnumberedsec from @heading in Texinfo?

> That way if the file has:
>
> #+OPTIONS: num:nil
>
> No TOC will be exported (even though the org-export-with-toc default is t).
>
> But if the file has:
>
> #+OPTIONS: num:nil toc:4
>
> As the toc value is a number, the TOC will be exported even though num is
> nil.

AFAICT, this doesn't solve any of the two concerns. What we can do for
"num:nil toc:4" can be done for "num:nil" alone.

Regards,



Re: [O] use %A to prompt for plain text when there is not file

2017-09-20 Thread Amos Bird

Um, but I'd like to use this template for both cases. When inside a temporary, 
don't generate a
link, but plain text instead, while in a file buffer, generate the link as 
usual.

regards,

Nicolas Goaziou  writes:

> Amos Bird  writes:
>
>> when in a file backed buffer, doing org capture with %A generates
>>
>>
>> [[some link][some description]]
>>
>> and if the buffer has no file associated with it, I'd like %A to generate
>>
>>
>> some description
>>
>> the above "some description" is inputed via prompting user.
>
> It sounds wrong to link to a temporary buffer, i.e., to volatile
> contents. It may be more appropriate to use
>
>  %^{prompt}
>
> in your template instead of
>
>  %A
>
> when capturing from there.
>
> WDYT?
>
> Regards,


--
Amos Bird
amosb...@gmail.com



Re: [O] What is the best way to show inline math formulas in org mode?

2017-09-20 Thread edgar

Hi Amos,

I am an inexpert user of Emacs, and that is why I think that I can help 
you. See the instructions below. Spoiler alert: the last line reads: "If 
you get your file .. I don't know how to help you."


The idea is:
1. Run emacs like this: emacs -Q
2. Check that you have a recent version of Emacs
   1) (assuming that you are running in linux) Check your Emacs version:
  a. [Alt] + [x] (in Emacs lingo, this translates to M-x, and lets 
you run commands)

  b. when you get a prompt, type  (without < >)
  c. type [Enter] (in Emacs lingo, this translates to RET most 
times)
   2) If you get a message with a version older than 24.4, your Emacs 
may be too old, but still work (may be).

3. Check that you have a recent version of Org
   Do the same as step 2, but replace  with 
. If your version is older than 8.7, I would suggest 
updating.

4. Check that you are actually running the right command
   1) Create a new buffer
  a. C-x b: [Control] + [x], then [b]
  b. test.org: type 
  c. RET
   2) Change onto org-mode by doing M-x org-mode RET
   3) Copy (kill) this as it is and paste it (yank it) on the buffer 
that you just created:   \(a = 2\)

   4) Put the cursor (point) on the <=> and do C-c C-x C-l
   5) If you don't see your equation, continue to step 5
5. If step 4 didn't work, make sure that you could produce the file in 
your computer

   1) Export the test.org to LaTeX by doing C-c C-e l l
   2) If it asks you for a name file, just type  (without < > 
!)

   3) Open the file (find the file): C-x C-f  (without < >)
   4) Do what you would normally do to produce your PDF
   5) If you get your file, it means that your Org configuration is not 
really working. Try testing your dvipng, dvisvgm or convert 
(imagemagick) commands. Imagemagick is not really good in terms of image 
quality, in my opinion, but you can play with the scale value (as 
suggested by Eric? Nicolas?). Other than that, I don't know how to help 
you.


-

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  



Re: [O] Add ability to force-enable TOC

2017-09-20 Thread Rasmus
Kaushal Modi  writes:

> On Tue, Sep 19, 2017 at 3:27 PM Nicolas Goaziou 
> wrote:
>
>> The change was intended. The idea was discussed on the ML. You may want
>> to check the thread.
>>
>> This is on par with, e.g., what LaTeX does.
>>
>
> What would be a good way, though, to bring back that functionality? I don't
> mind if I need to set extra options/variables for that.

In the case of LaTeX you could do:

#+latex_header: \setcounter{secnumdepth}{0}
#+options: toc:3

For what it’s worth, I don’t think the new behavior is correct, seeing
Kaushal’s example.

The option "num" touches secnumdepth (in ox-latex).  But setting that does
not imply that all headings should be constructed with their starred
variant (e.g. "\section*{.}").

IMO, this behavior should be reverted in maint as it would be nice to
include 9.1 in the next version of Emacs.

Rasmus

-- 
This message is brought to you by the department of redundant departments




[O] Doc bug: Publishing "Simple Example" is missing publishing function

2017-09-20 Thread Nick Dokos
I tried to publish the project described in

  (info "(org) Simple example")

and I got the complaint

,
| ~$ emacs -batch -l foo.el --eval '(org-publish "org")'
| No publishing function chosen
`

I attach a patch to fix the doc.

>From 653cf7ba3041c5992091317f0c18c47326f58d70 Mon Sep 17 00:00:00 2001
From: Nick Dokos 
Date: Wed, 20 Sep 2017 08:03:49 -0400
Subject: [PATCH] Add publishing function to "Simple example"

The simple example project definition is missing a publishing
function. Added org-html-publish-to-html as the publishing function.
---
 doc/org.texi | 1 +
 1 file changed, 1 insertion(+)

diff --git a/doc/org.texi b/doc/org.texi
index b368c0e..53143df 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -15024,6 +15024,7 @@ directory on the local machine.
   '(("org"
  :base-directory "~/org/"
  :publishing-directory "~/public_html"
+ :publishing-function org-html-publish-to-html
  :section-numbers nil
  :with-toc nil
  :html-head "
-- 
Nick




Re: [O] Add ability to force-enable TOC

2017-09-20 Thread Rasmus
Carsten Dominik  writes:

> That may be so, but I find that unfortunate.  I am really using this
> feature often.
>
> I will go back and take a look at this thread.  Can someone tell me what
> the subject line of that thread was?

I think it’s this one.

Subject: setting local variables
Date: Thu, 07 Sep 2017 14:48:03 +0200 (and earlier)

Rasmus

-- 
May the Force be with you




Re: [O] Add ability to force-enable TOC

2017-09-20 Thread Kaushal Modi
On Wed, Sep 20, 2017, 6:25 AM Nicolas Goaziou 
wrote:

> I didn't say it was an unusual case. I said it didn't cover all the
> use-cases. Maybe you are really needing a subset of the initial feature.
>

Understood.

IOW, do mixed numbered/unnumbered headings make sense in TOC?
>

Correct. That does not make sense to me. That is not my use case.

>> 1. it makes all export back-ends consistent with TOC;
> >>
> >
> >  I understand that. But would like a way to get back the earlier behavior
> > too.
>
> Then there is the other way around: how do we tell LaTeX to include both
> numbered and unnumbered headings?
>

I see your point.

AFAICT, this doesn't solve any of the two concerns. What we can do for
> "num:nil toc:4" can be done for "num:nil" alone.
>

That might work.. treat num:nil differently than num:0

So here's the summary as per my understanding.

Currently we support these:

1. Don't allow a mix of numbered and unnumbered headings in TOC. If any
heading is unnumbered using the UNNUMBERED property, remove it from the
TOC.

2. If we globally unnumber headings beyond a certain level by doing
something like num:3, don't show headings beyond that level in the TOC. So
num:0 wouldn't number any heading and also not generate the TOC.

Now the 3rd use case (mine):

3. Unnumber all headings, but still keep them in TOC.

So allow this 3rd use case when, may be, we have num:nil and not num:0?

WDYT?

@Carsten: Does this satisfy your use case too?

> --

Kaushal Modi


Re: [O] use %A to prompt for plain text when there is not file

2017-09-20 Thread Nicolas Goaziou
Hello,

Amos Bird  writes:

> I'm currently using this template,
> #+BEGINEXAMPLE
>
> 1 %A [/]
>
> * [ ] %?
>
> #+ENDEXAMPLE
>
> However when capturing in a non-file buffer, %A generates nothing. I'd like 
> to have a plain text inserted instead. What can I do?

What do you mean by "a plain text inserted"? Could you give an example?

Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] Confused about the explanation for 'org-cycle'

2017-09-20 Thread Nicolas Goaziou
Hello,

Matt Lundin  writes:

> I agree that this is confusing. I examined the org repository history,
> and it seems that both the documentation and the variable go all the way
> back to 2007. I believe the default value of the variable was changed to
> nil, but the documentation was not updated accordingly.

I rewrote the part about `org-cycle-global-at-bob'. Hopefully it is
clearer now.

Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: Babel Tramp python [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.3/lisp/org/)]

2017-09-20 Thread Nicolas Goaziou
Hello,

emacswatc...@gmail.com writes:

> Given emacs -Q with this file:
>
> +++ test.org
>
> #+TITLE:  Babel remote processing test
> #+AUTHOR: jjh
>
> #+EMAIL:  emacswatc...@gmail.com
>
> * python
>
> #+BEGIN_SRC python :dir /ssh:root@[some remote host]:
>   import socket
>   return ("Hostname is %s" % socket.gethostname())
> #+END_SRC
>
> --- test.org
>
> and with python added to org-babel-language-list:
>
> (setq org-babel-load-languages
>  ((python . t)
>   (sh . t)
>   (emacs-lisp . t)))
>
> executing the source block with a valid remote host returns in *Messsages*:
>
> executing Python code block...
> Tramp: Encoding local file ‘/tmp/tramp.1353PZN’ using 
> ‘base64-encode-region’...done
> Tramp: Decoding remote file ‘/ssh:root@[my remote host]:/tmp/python-1353CPH’ 
> using ‘base64 -d -i >%s’...done
> org-babel-local-file-name: Invalid function: with-parsed-tramp-file-name

This sounds like an issue with Emacs/Tramp, not Org. Org calls
`file-local-name', if it exists (since Emacs 26.0.50) or `file-remote-p'
otherwise. In particular, it doesn't call `with-parsed-tramp-file-name'
directly.

Regards,

-- 
Nicolas Goaziou



Re: [O] use %A to prompt for plain text when there is not file

2017-09-20 Thread Nicolas Goaziou
Amos Bird  writes:

> when in a file backed buffer, doing org capture with %A generates
>
>
> [[some link][some description]]
>
> and if the buffer has no file associated with it, I'd like %A to generate
>
>
> some description
>
> the above "some description" is inputed via prompting user.

It sounds wrong to link to a temporary buffer, i.e., to volatile
contents. It may be more appropriate to use

 %^{prompt}

in your template instead of

 %A

when capturing from there.

WDYT?

Regards,



Re: [O] use %A to prompt for plain text when there is not file

2017-09-20 Thread Amos Bird
#+OPTIONS: latex:t toc:nil H:3

Hi Nicolas,

when in a file backed buffer, doing org capture with %A generates
#+BEGIN_EXAMPLE
[[some link][some description]]
#+END_EXAMPLE
and if the buffer has no file associated with it, I'd like %A to generate
#+BEGIN_EXAMPLE
some description
#+END_EXAMPLE

the above "some description" is inputed via prompting user.

regards,

Nicolas Goaziou  writes:

> Hello,
>
> Amos Bird  writes:
>
>> I'm currently using this template,
>> #+BEGINEXAMPLE
>>
>> 1 %A [/]
>>
>> * [ ] %?
>>
>> #+ENDEXAMPLE
>>
>> However when capturing in a non-file buffer, %A generates nothing. I'd like 
>> to have a plain text inserted instead. What can I do?
>
> What do you mean by "a plain text inserted"? Could you give an example?
>
> Thank you.
>
> Regards,


--
Amos Bird
amosb...@gmail.com


Re: [O] Add ability to force-enable TOC

2017-09-20 Thread Rasmus
Rasmus  writes:

> IMO, this behavior should be reverted in maint as it would be nice to
> include 9.1 in the next version of Emacs.

I misunderstood the initial report.  Ignore the above.

I don’t understand why, in ox-latex, "num" sets both
"\setcounter{secnumdepth}{.}"  and switches to "section*" and friends.
Setting "\setcounter{secnumdepth}{.}" is enough to get unnumbered
headlines...

Rasmus

-- 
C is for Cookie




Re: [O] Add ability to force-enable TOC

2017-09-20 Thread Kaushal Modi
On Wed, Sep 20, 2017, 4:14 AM Carsten Dominik  wrote:

>
> I will go back and take a look at this thread.  Can someone tell me what
> the subject line of that thread was?
>

http://lists.gnu.org/archive/html/emacs-orgmode/2017-09/msg00157.html
-- 

Kaushal Modi


Re: [O] setting local variables

2017-09-20 Thread Carsten Dominik
On Thu, Sep 7, 2017 at 5:01 PM, Eric Abrahamsen 
wrote:

> Nicolas Goaziou  writes:
>
>
> [...]
>
> > So, any objection to have all major back-ends ignoring unnumbered trees
> > from TOC, and make that an Org specificity?
>


Hi Nicolas,

OK, now I have read this thread.

I do object to removing unnumbered headers from the toc.  It breaks
documented and used behaviour and aI see no pressing reason to change it. I
find, for compact documents, it works extremely well to have a toc that has
no numbers - in fact, in many cases I find numbered tocs even annoying.  In
particular, it works really well in websites, where I use it constantly.

I am sorry that I did not see this earlier - but I really think this change
should be reverted.  If there is a desire to have sections that are not put
into the toc, it should be separated from the num: and toc: switches and
depend, for example on properties instead.

The fact that in LaTeX "unnumbered" is linked to the question if something
is in the toc is some kind of mistake, this behaviour is very specific to
LaTeX-like systems (including TeXInfo), but it is not a very logical system
IMO.

Carsten


>
> Sounds good!
>
>
>


[O] [PATCH] Implement Org pdfview

2017-09-20 Thread Oleg Pykhalov
Hello Emacs Org,

I prepared pdf-view based on doc-view for org-capture.

--8<---cut here---start->8---
guix environment emacs-org -- make test
…
org-pdfview.el:102:1:Warning: the function ‘pdf-view-current-page’ is not
known to be defined.
…
Ran 738 tests, 738 results as expected (2017-09-20 18:39:25+0300)
13 expected failures
--8<---cut here---end--->8---

>From 4d1a7452f9dfd06e9730ceafd3fefb5bea52e3ec Mon Sep 17 00:00:00 2001
From: Oleg Pykhalov 
Date: Wed, 20 Sep 2017 18:14:26 +0300
Subject: [PATCH] Implement Org pdfview

* lisp/org-pdfview.el: New file.
---
 lisp/org-pdfview.el | 101 
 1 file changed, 101 insertions(+)
 create mode 100644 lisp/org-pdfview.el

diff --git a/lisp/org-pdfview.el b/lisp/org-pdfview.el
new file mode 100644
index 0..ebfcfef14
--- /dev/null
+++ b/lisp/org-pdfview.el
@@ -0,0 +1,101 @@
+;;; org-pdfview.el --- Support for links to pdf-view-mode buffers -*- lexical-binding: t; -*-
+
+;; Copyright (C) 2009-2017 Free Software Foundation, Inc.
+
+;; Author: Oleg Pykhalov 
+;; Keywords: outlines, hypermedia, calendar, wp
+;; Homepage: http://orgmode.org
+;;
+;; This file is part of GNU Emacs.
+;;
+;; GNU Emacs is free software: you can redistribute it and/or modify
+;; it under the terms of the GNU General Public License as published by
+;; the Free Software Foundation, either version 3 of the License, or
+;; (at your option) any later version.
+
+;; GNU Emacs is distributed in the hope that it will be useful,
+;; but WITHOUT ANY WARRANTY; without even the implied warranty of
+;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+;; GNU General Public License for more details.
+
+;; You should have received a copy of the GNU General Public License
+;; along with GNU Emacs.  If not, see .
+;
+;;
+;;; Commentary:
+
+;; This file implements links to open files in pdf-view-mode.
+;; Org mode loads this module by default - if this is not what you want,
+;; configure the variable `org-modules'.
+
+;; The links take the form
+;;
+;;pdfview:::
+;;
+;; for example: [[pdfview:~/.elisp/org/doc/org.pdf::1][Org-Mode Manual]]
+;;
+;; Autocompletion for inserting links is supported; you will be
+;; prompted for a file and a page number.
+;;
+;; If you use org-store-link in a pdf-view mode buffer, the stored
+;; link will point to the current page.
+
+;;; Code:
+
+
+(require 'org)
+
+(declare-function pdf-view-goto-page "pdf-view" (page))
+
+(org-link-set-parameters "pdfview"
+			 :follow #'org-pdfview-open
+			 :export #'org-pdfview-export
+			 :store #'org-pdfview-store-link)
+
+(defun org-pdfview-export (link description format)
+  "Export a pdfview link from Org files."
+  (let* ((path (if (string-match "\\(.+\\)::.+" link) (match-string 1 link)
+		 link))
+ (desc (or description link)))
+(when (stringp path)
+  (setq path (org-link-escape (expand-file-name path)))
+  (cond
+   ((eq format 'html) (format "%s" path desc))
+   ((eq format 'latex) (format "\\href{%s}{%s}" path desc))
+   ((eq format 'ascii) (format "%s (%s)" desc path))
+   (t path)
+
+(defun org-pdfview-open (link)
+  (string-match "\\(.*?\\)\\(?:::\\([0-9]+\\)\\)?$" link)
+  (let ((path (match-string 1 link))
+	(page (and (match-beginning 2)
+		   (string-to-number (match-string 2 link)
+;; Let Org mode open the file (in-emacs = 1) to ensure
+;; org-link-frame-setup is respected.
+(org-open-file path 1)
+(when page (pdf-view-goto-page page
+
+(defun org-pdfview-store-link ()
+  "Store a link to a pdfview buffer."
+  (when (eq major-mode 'pdf-view-mode)
+;; This buffer is in pdf-view-mode
+(let* ((path buffer-file-name)
+	   (page (pdf-view-current-page))
+	   (link (concat "pdfview:" path "::" (number-to-string page
+  (org-store-link-props
+   :type "pdf-view"
+   :link link
+   :description path
+
+(defun org-pdfview-complete-link ()
+  "Use the existing file name completion for file.
+Links to get the file name, then ask the user for the page number
+and append it."
+  (concat (replace-regexp-in-string "^file:" "pdfview:" (org-file-complete-link))
+	  "::"
+	  (read-from-minibuffer "Page:" "1")))
+
+
+(provide 'org-pdfview)
+
+;;; org-pdfview.el ends here
-- 
2.14.1



Re: [O] setting local variables

2017-09-20 Thread Scott Randby


On 09/20/2017 12:17 PM, Carsten Dominik wrote:
> On Thu, Sep 7, 2017 at 5:01 PM, Eric Abrahamsen 
> wrote:
> 
>> Nicolas Goaziou  writes:
>>
>>
>> [...]
>>
>>> So, any objection to have all major back-ends ignoring unnumbered trees
>>> from TOC, and make that an Org specificity?
>>
> 
> 
> Hi Nicolas,
> 
> OK, now I have read this thread.
> 
> I do object to removing unnumbered headers from the toc.  It breaks
> documented and used behaviour and aI see no pressing reason to change it. I
> find, for compact documents, it works extremely well to have a toc that has
> no numbers - in fact, in many cases I find numbered tocs even annoying.  In
> particular, it works really well in websites, where I use it constantly.
> 
> I am sorry that I did not see this earlier - but I really think this change
> should be reverted.  If there is a desire to have sections that are not put
> into the toc, it should be separated from the num: and toc: switches and
> depend, for example on properties instead.
> 
> The fact that in LaTeX "unnumbered" is linked to the question if something
> is in the toc is some kind of mistake, this behaviour is very specific to
> LaTeX-like systems (including TeXInfo), but it is not a very logical system
> IMO.
> 
> Carsten

I have to agree with Carsten. I use unnumbered table of contents all the time 
in web pages. Almost all of my Org files that generate web pages have the 
following:

#+options: num:nil toc:t

The change should be reverted. I wish I had paid attention to this thread. I 
thought it was about something else.

Scott Randby

> 
> 
>>
>> Sounds good!
>>
>>
>>
> 



Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?

2017-09-20 Thread Lars-Johan Liman
Loris Bennett writes:
>> Having said that, having let my .emacs grow organically (think "rampant
>> weeds") for 30 years, maybe I should take the shears to it.

:-) :-) Hahaa! LOL! I was thinking exactly those words earlier this
morning, while trying to debug a complicated "cond" statement that tries
to figure out on which computer the Emacs is being starting, and which
windowing system is being used on it.

But I've stopped trying to maintain my PS:EMACS.INIT. (Is anyone
else that old? :-) My TECO is getting rusty ... ;-)

theophil...@gmail.com:
> Management of an emacs init file is a challenge for anyone who has been
> using Emacs for a long time.

I have some files in CVS (yes, I'm that old ;-), but yes, Git is on my
mind too. Every new thing I archive I put in Git.

But, this looked interesting ...

> 3. I now use org to manage my init file. In fact, I have a few init
> files. I have a bare bones minimal init file which I use when I need to
> debug a specific feature/package or generate bug reports, I have an
> experimental one where I play with new things and I have my stable
> one. Using org, I can just 'tangle' a new init based on one of those
> files whenever I need it. I started by just putting all my existing
> setup into a block in an org file and exporting that as elisp. As time
> permitted, I broke bits off into their own blocks with explanatory
> comments/text so that I can remember why/what of the block.

Can you expand on how using Org for this is done? Examples?
Documentation?

Cheers,
  /Liman
#-
# Lars-Johan Liman, M.Sc.! E-mail: li...@cafax.se
# Cafax AB   ! HTTP  : //www.cafax.se/
# Computer Consultants, Sweden   ! Voice : +46 8 - 564 702 30
#-



Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?

2017-09-20 Thread Eric S Fraga
On Wednesday, 20 Sep 2017 at 15:49, Lars-Johan Liman wrote:

[...]

> I have some files in CVS (yes, I'm that old ;-), but yes, Git is on my
> mind too. Every new thing I archive I put in Git.

Hey, I still use RCS... :-)

But, okay, I do use git and mercurial as well.  Have to go with the flow
sometimes.

And parts of my .emacs date back to the mid-80s.  Probably due a clean up
sometime soon but why tinker with something that works...

-- 
: Eric S Fraga via Emacs 26.0.50, Org release_9.0.9-573-g09e612


signature.asc
Description: PGP signature


Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?

2017-09-20 Thread Thomas S. Dye
Aloha,

Lars-Johan Liman writes:

>> 3. I now use org to manage my init file. In fact, I have a few init
>> files. I have a bare bones minimal init file which I use when I need to
>> debug a specific feature/package or generate bug reports, I have an
>> experimental one where I play with new things and I have my stable
>> one. Using org, I can just 'tangle' a new init based on one of those
>> files whenever I need it. I started by just putting all my existing
>> setup into a block in an org file and exporting that as elisp. As time
>> permitted, I broke bits off into their own blocks with explanatory
>> comments/text so that I can remember why/what of the block.
>
> Can you expand on how using Org for this is done? Examples?
> Documentation?
>
>   Cheers,
> /Liman
> #-
> # Lars-Johan Liman, M.Sc.  ! E-mail: li...@cafax.se
> # Cafax AB ! HTTP  : //www.cafax.se/
> # Computer Consultants, Sweden ! Voice : +46 8 - 564 702 30
> #-

An example from a few years ago is here:
https://github.com/eschulte/emacs24-starter-kit

hth,
Tom

--
Thomas S. Dye
http://www.tsdye.com



Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?

2017-09-20 Thread Nick Dokos
"Loris Bennett"  writes:

> I might even go wild and move to init.el ;-)
>

I moved to init.el a long time ago and now things are worse than they
ever were with .emacs: there is all the .emacs crud that I copied over
*plus* all the new init.el crud that I've added since I switched.
I can't wait for bigger-better-init.el to be the new fad, so I can
rename^H^H^H^H^H^Hclean up init.el...

-- 
Nick




Re: [O] setting local variables

2017-09-20 Thread Kaushal Modi
On Wed, Sep 20, 2017, 2:43 PM Scott Randby  wrote:

>
>
> On 09/20/2017 12:17 PM, Carsten Dominik wrote:
> > On Thu, Sep 7, 2017 at 5:01 PM, Eric Abrahamsen  >
> > wrote:
> > I do object to removing unnumbered headers from the toc.


I believe this change was made to fix the case of mixed numbered and
unnumbered headings in the TOC.

Please see the other thread[1] where I suggest supporting the "case 3"
where we want TOC where all headings are numbered i.e. the case of num:nil.

 It

breaks
> > documented and used behaviour and aI see no pressing reason to change
> it. I
> > find, for compact documents, it works extremely well to have a toc that
> has
> > no numbers - in fact, in many cases I find numbered tocs even annoying.
> In
> > particular, it works really well in websites, where I use it constantly.
>

Mine is the same use case and the num:nil case covers that.

 I have to agree with Carsten. I use unnumbered table of contents all the
> time in web pages. Almost all of my Org files that generate web pages have
> the following:
>
> #+options: num:nil toc:t
>

@Scott Please see that other thread[1]. I have this exact use case. And if
the case 3 discussed in that thread is supported all should be good.

[1]: http://lists.gnu.org/archive/html/emacs-orgmode/2017-09/msg00497.html
-- 

Kaushal Modi


Re: [O] Bug: org-emphasis-alist not fully applied [9.1.1 (9.1.1-1-g80cbf9-elpa @ x:/folder/user/.emacs.d/elpa/org-20170918/)]

2017-09-20 Thread Jens Lange
Thanks, for that information. Since I have no coding knowlege I reached out
to stackexchange for some help for a workaround. Question is here:
https://emacs.stackexchange.com/questions/35626/how-to-make-my-own-org-mode-text-emphasis-work-again

One guy mentioned this after I wrote about this bug report:

"If they don't want items added to org-emphasis-alist they shouldn't use
the repeat customization type which allows insertion and deletion.
Furthermore, they should add a note about this restriction in the doc
string of org-emphasis-alist. Maybe, you can give a follow-up in the
bug-report about that."

So I did what he requested. He also provided me with a working solution.
Even with that said I might ask if you could consider supporting adding new
emphasis definitions in the future? For people like me who are not able to
write a function to solve the problem in an instant this customize option
is like the red carpet already lying on the floor.

With kind regards,
Jens Lange

2017-09-19 21:23 GMT+02:00 Nicolas Goaziou :

> Jens Lange  writes:
>
> > Hmm, but that worked until recently. Without any hook.
> >
> > Or was your answer like: Good for you that it worked in the past but
> since
> > it ain't supported we won't make it work again?
>
> That's more like it, sorry. The fact that it worked doesn't mean it was
> supported.
>
> As I suggested there are other ways to achieve what you want.
>
> Regards,
>



-- 
Mit freundlichen Grüssen / With kind regards:
Jens Lange