Hello,
Jens Lechtenboerger writes:
> currently, we have to write the following to continue an ordered
> list from a value different from 1:
>
> 42. [@42] Answer
> 43. Question?
>
> The requirement to type redundant information with the @-syntax
> always struck me as odd. For my export backend
Colin Baxter writes:
>> David Masterson writes:
>
> > My use-case is this: I'd like to use Org to write up *all* the
> > information about my family life (so to speak) including medical
> > histories of my family, issues with the house, bank accounts,
> > financial
w...@mm.st writes:
> 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
I have one scheduled item like the following:
* test
<2019-12-05 Thu 23:00-29:00>
This kind of item fails to be parsed by agenda because of incorrect
treatment of 23:00-29:00 time interval
Specifically, calling
(org-agenda-format-item nil #("test" 0 3 (face org-level-1 org-category
"schedule"
I often have several different babel languages in the same file. I'd
like to be able make them easily distinguished by language (such as
having a different background or shadow).
As far as I can tell, the listings package doesn't let me override
settings by language.
The best solution I've so
[note: id markers use org ids.]
On 12/1/19, Samuel Wales wrote:
> i think it might be partlly a question of whether these numbers are
> fixed things that refer to fixed items [like referring to sections in
> a law that is not in the document] vs. being used to continue lists.
>
> they are both
i think it might be partlly a question of whether these numbers are
fixed things that refer to fixed items [like referring to sections in
a law that is not in the document] vs. being used to continue lists.
they are both legitimate uses. in the first case, the @ syntax makes
sense to me, because
Hi there,
currently, we have to write the following to continue an ordered
list from a value different from 1:
42. [@42] Answer
43. Question?
The requirement to type redundant information with the @-syntax
always struck me as odd. For my export backend org-re-reveal, I
recently received a
There is already org-image-actual-width but the problem with that one is
that images that have quite small width, but are tall will be scaled and
become very tall.
I think it would make sense to introduce something like
org-image-max-width, which would scale images that are larger than this
This adds a feature similar to the org-fontify-done-headline, but
instead for the TODO headlines.
This is enabled with the boolean customization org-fontify-todo-headline
and can be themed via the face org-headline-todo.
I was missing this when I wanted to distinguish more clearly between the
Hello all,
I use column view quite a lot. Very useful, especially for editing
properties. I also use it for task management, having moved to Marcin
Swieczkowski's approach [1]. For managing my tasks, the column view I
have defined includes scheduled and deadline dates. I would like to be
able
On 01 Dec 2019, Marco Wahl wrote:
>I guess it's a good idea to write to Bastien explicitly.
I will do so.
>Thanks for asking about the version. AFAICT there is a feature freeze
>right now for version 9.3. This means you would commit to the 'next'
>branch which shall be the next master branch
Hi Karl,
>>I think your enhancement is great and worth a news entry. What about
>>pushing your code if nobody objects within one week?
>
> Thanks, Marco; I'm glad you like it. I'll wait a week and then push
> (unless there's discussion, in which case we'll see what the outcome
> of the
On 01 Dec 2019, Marco Wahl wrote:
>+1
>
>I think your enhancement is great and worth a news entry. What about
>pushing your code if nobody objects within one week?
Thanks, Marco; I'm glad you like it. I'll wait a week and then push (unless
there's discussion, in which case we'll see what the
Karl Fogel writes:
> This is the enhancement to `org-narrow-to-subtree' that I suggested back in
> May [1].
>
> It allows you to choose what level subtree to narrow to. There are
> two ways to specify the subtree: use repeated C-u's to select "upward"
> from the current subtree, or use a
Soubzriquet writes:
>> [...]
>> > odd issue with using "day" steps where the date is getting offset
>> > sometimes.
>> >
>> > I saw the issue with 26.1, was not fixed by updating to current
>> > environment with an empty init.el on OS X:
>> [...]
>>
>> > * Day 1
>> > :LOGBOOK:
>> > CLOCK:
On Saturday, 30 Nov 2019 at 18:37, Pankaj Jangid wrote:
> It converts the text in the message buffer into multipart message. But
> the conversion doesn't work well at the point of signature.
For these cases, I usually put a colon at the start of each line of the
signature which htmlize then
Nicolas Goaziou writes:
>> Any hope of this super tiny patch being applied? It addresses the
>> problem I brought up in another thread: it is currently not possible
>> to pass command line arguments to a java program.
>
> Org 9.3 is feature frozen for the time being. Do you think this
>
This is the enhancement to `org-narrow-to-subtree' that I suggested back in May
[1].
It allows you to choose what level subtree to narrow to. There are two ways to
specify the subtree: use repeated C-u's to select "upward" from the current
subtree, or use a direct numeric prefix arg to
19 matches
Mail list logo
