Re: Automatic Capture of Heading Creation Time In Certain Files?

2020-03-15 Thread wry

I would like to automatically have the results of a double prefixed call to
`org-time-stamp-inactive` inserted as the body of new TODO entries.


Have you tried including %U in your template? See "Template expansion"
in the Org Mode documentation:

("t" "Full task capture" entry (file+headline "~/org/tasks.org"
 "INBOX") "* TODO %?\n%iAdded: %U")


https://five.sentenc.es


Heads up, the ssl on https://five.sentenc.es/ is broken.



Re: Bug: org-html-export-to-html doesn't handle .gpg files properly [9.3.6 (9.3.6-17-g389288-elpa @ /home/adalricus/.emacs.d/elpa/org-20200224/)]

2020-03-08 Thread wry

- create a file called "test.org.gpg"
- run org-html-export-to-html

File gets exported as test.org.html, shouldn't it be test.html?


I don't know the answer, but I just use files without the .org
(e.g. "test.gpg") and set up encryption with org's in-buffer settings:

# -*- mode:org; epa-file-encrypt-to: ("em...@example.com") -*-





signature.asc
Description: PGP signature


Re: How do i configure org-publish-project-alist for multiple projects for html generation?

2020-03-01 Thread wry

You can use a main directory with subdirectories with the

:recursive t

option, or have multiple projects defined and run
org-publish-all



Re: need to increase contrast in all emacs faces for legibility

2019-12-11 Thread wry

On 12/10, Samuel Wales wrote:

at night, i need much more contrast in my emacs faces in order to
increase legibility.


This is counterintuitive, normally you need to increase contrast
during the day and decrease contrast (and lower brightness) at night
to prevent eye strain. Unless you're using an E Ink display or
something crazy, decreased ambient light should not affect legibility
(pixels are backlit), only eye strain.


is it possible to programmatically increase foreground contrast
against their background in all faces?



i already have the background black or close to it.


Studies have suggested that light text on dark background is less
legible than dark text on light background, so you could change
that. Anecdotally this is true for me in Emacs and on the web, but the
decreased eye strain at night is worth the tradeoff of using a dark
background.

I doubt Emacs has this contrast functionality built in. You can always
change themes (M-x customize-themes). A quick Google of "Emacs high
contrast themes" yields at least one theme you could try.

You can even manually modify themes. Just go to the Elisp file and
play around with the theme definition. Use Gimp or Google "HTML color
picker" to find new colors to replace whichever color you're not
satisfied with.

If you're actually trying to reduce eye strain at night, there are
several tools at your disposal.

- Redshift has already been mentioned; I consider my computer
 basically unusable at night without it
- Decrease display brightness using software
 (e.g. https://github.com/haikarainen/light )
- Change brightness or color settings at the hardware level (by
 clicking buttons on your monitor)
- Add more ambient light around your monitor
- Computer blue-light filtering glasses (I don't know if they're effective or 
not)



Re: Org export to HTML with encrypted information ??

2019-11-29 Thread wry

Hi,
Here's a simpler flow. See if it would support your use case:

Modern PDF readers support password
encryption. org-latex-export-to-pdf, then encrypt the file and share
it with your family. If you want to keep it offline, give them USB
drives. It's not too late to get black Friday deals on the 2.0 sticks.

Write the password on a sticky note and stick it on your fridge. 


If you're worried about the integrity of the org file on your own
computer, make it a .gpg file instead, and stick something like:

# -*- mode:org; epa-file-encrypt-to: ("y...@email.com") -*-

at the top.

Nick



Re: Question: export with tags but hide "export" tag

2019-11-24 Thread wry

On 11/24, Fraga, Eric wrote:

You could maybe use this hook:

,[ C-h v org-export-before-processing-hook RET ]
| org-export-before-processing-hook is a variable defined in ‘ox.el’.
|
| Documentation:
| Hook run at the beginning of the export process.
|
| This is run before include keywords and macros are expanded and
| Babel code blocks executed, on a copy of the original buffer
| being exported.  Visibility and narrowing are preserved.  Point
| is at the beginning of the buffer.
|
| Every function in this hook will be called with one argument: the
| back-end currently used, as a symbol.
`

*if* it is invoked after the tag selection is done (I'm not sure if it
is or not).  You would have to write some emacs lisp to remove the
:export: tags.


Thanks, I'll look into it. Probably should brush up on my elisp anyway

Nick



Question: export with tags but hide "export" tag

2019-11-23 Thread wry

Hi fellow org people,

I want to start publishing some of my notes on a website. My preferred
method is either org-export-dispatch or org-publish (maybe in the
future).

I have one giant notes file where I keep everything. Some people
prefer to have multiple files to compartmentalize, but I prefer to
keep everything together to simplify searching, organizing, capturing
etc. This is similar to the philosophy of dnote (a third-party,
non-org-mode note taking app at https://www.getdnote.com/): being able
to capture a note as quickly as possible is more important than
putting it in the correct place, and being able to search all notes is
more important than having them perfectly organized.

Towards the top of the file are more permanent entries, like my TODO
inbox, calendar, and daily checklist. Whenever I add a note, I
automatically stick it at the end of the file. When headlines are
completed or become more permanent, I sometimes refile them higher up
in the file ("percolate up", if you will).

Anyway, my preferred method of publishing would be to simply tag
headlines when they're ready to be included in HTML exports. Org-mode
includes this, of course, with the "org-export-select-tags"
option. However, I also want to include tags in the exported HTML, but
currently that means every exported headline will have the "export"
tag. Any ideas about how to export using this workflow without showing
the "export" tag?

Thanks,
Nick