On 25 May 2022, Uwe Brauer wrote:
Sometimes I only want to convert/export a region or a paragraph of an
org file to another format, most likely as html or latex.
Is this different from subtree export? After C-c C-e, C-s will toggle "export
scope" between buffer and subtree. (There's also
Thanks! Precise as always.
I'm not sure if it's the best way to do so, but it worked for me by
using a lambda:
(setq citar-file-open-function '(lambda (file)
(async-shell-command (format-message "sioyek \"%s\"" file
Moreover, since I don't really care about the terminal output of
"Samuel Banya" writes:
> Appreciate the offer for Saturday, but I have to take care of something on
> Saturday. What time slots were you thinking in EDT?
All previous meetings were 9am EDT I think.
https://orgmode.org/list/87pmksgx3l.fsf@localhost
Best,
Ihor
Just curious:
I'm not familiar with Sioyek (though it looks cool!); why do you need
a lambda there?
On Wed, May 25, 2022 at 10:10 AM Alessandro Bertulli
wrote:
>
> Thanks! Precise as always.
>
> I'm not sure if it's the best way to do so, but it worked for me by
> using a lambda:
>
> (setq
Hi
Sometimes I only want to convert/export a region or a paragraph of an
org file to another format, most likely as html or latex.
I cannot find such a functionality also not in the package system
does anybody knows about such a function?
Regards
Uwe Brauer
--
I strongly condemn Putin's
Thanks for the suggestion! I wasn't aware of shell-quote-argument, now
it seems much more robust:
(setq citar-file-open-function '(lambda (file)
(async-shell-command (format-message
"sioyek %s" (shell-quote-argument
On 25/05/2022 14:22, Ihor Radchenko wrote:
Max Nikulin writes:
On 24/05/2022 09:51, Timothy wrote:
To me, this is another reason for comment and #+attr_X lines not to break
paragraphs, as then we can just re-use #+attr_X lines.
I will raise a compatibility issue, but it is bad enough to not
It's a PDF viewer that tries to display scientific and academic writings
at his best. It's actually still experimental, in a way, but it looks
promising and, for now, I don't have big problems. Unfortunately, it has
vi-style keybindings :-)
Anyway, I think I need a lambda because there's not a
On 25/05/2022 23:00, Bruce D'Arcus wrote:
On Wed, May 25, 2022 at 11:26 AM Max Nikulin wrote:
On 25/05/2022 18:00, Bruce D'Arcus wrote:
You just need to set `citar-file-open-function` to your preferred
function; say xdg-open.
Is there a reason to avoid emacs global or even system global
Max Nikulin writes:
> On 22/05/2022 11:10, Ihor Radchenko wrote:
>> Max Nikulin writes:
>>
>>> The source of the problem is that Emacs-27 was released with the
>>> following bug:
>>>
>>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40247
>>> mailcap-mime-data erased when parsing mime parts
>>>
Eric S Fraga writes:
> sorry to revisit this but I continue to run into the problem of the
> bibliography not being rescanned automatically. What is the easiest way
> (other than leaving Emacs and restarting) to force it, assuming there is
> one? I.e. maybe I can invalidate or clear the cache?
Matt Lundin writes:
> I just noticed also that the name has been changed to
> org-cycle-force-archived and that the key index reference was incorrect.
> I've attached an additional patch to fix these in the manual.
Thanks! Applied onto main via 292116b62.
Best,
Ihor
"Aaron L. Zeng" writes:
> (I'm resubmitting this patch because my previous submission was in-reply-to
> another email which I suspect was ignored. Would love to get this relatively
> simple bug fixed. Thanks!)
>
> * lisp/org.el (org-todo-yesterday): Fix an incorrect use of apply when
>
Thanks Ihor! And, noted for the future.
On Thu, May 26, 2022 at 12:34 AM Ihor Radchenko wrote:
> "Aaron L. Zeng" writes:
>
> > (I'm resubmitting this patch because my previous submission was
> in-reply-to
> > another email which I suspect was ignored. Would love to get this
> relatively
> >
Daniel Fleischer writes:
> Ihor Radchenko [2022-05-22 Sun 11:51] wrote:
>
>> The attached patch is fixing a rather annoying problem when
>> org-latex-pdf-process is set to a list. Currently, only output of the
>> last command in the list is preserved in *Org PDF LaTeX output* buffer,
>> which
Uwe Brauer writes:
> It seems that I did not check this carefully enough. Indeed, if I mark a
> region and run the export function, only the active region will be
> exported. The docstring of that function is, however, not that clear
> about it.
Could you please clarify which part of the
Max Nikulin writes:
>> First line
>> # comment
>> Second line
>>
>> Should we consider a comment as inline object? I suspect that such
>> change will cause unpredictable breakages all around Org and third-party
>> packages.
>
> I believed that comments are stripped before passing to export
thank you for that /very/ useful information. cannot seem to
reproduce at this time as i'd have to narrow down the dialog box in
which this occurs [i think on a save link in gmail with some
extensions or so is one place] for haelth reasons but i think part of
the problem is that .emacs is not
Richard Stanton writes:
> Odd. Invoking it as you do on my Mac, I get the same results I noted earlier.
Then, can you ask some other Mac user to reproduce? It is hard to fix
something not reproducible on my system :(
Or maybe we can arrange a live screensharing to directly debug the issue
on
Max Nikulin writes:
> On 22/05/2022 10:51, Ihor Radchenko wrote:
>>
>> The attached patch is fixing a rather annoying problem when
>> org-latex-pdf-process is set to a list. Currently, only output of the
>> last command in the list is preserved in *Org PDF LaTeX output* buffer,
>> which
João Pedro writes:
>> #+attr_latex[name]:
>> Vestibulum convallis, lorem blockname_[<>]{text} a tempus semper, dui
>> dui euismod elit, vitae placerat urna tortor vitae lacus.
>>
>> "<>" will be treated as "" during
>> export/parsing.
>
> Although I do agree that this sort of solves the same
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> It seems that I did not check this carefully enough. Indeed, if I mark a
>> region and run the export function, only the active region will be
>> exported. The docstring of that function is, however, not that clear
>> about it.
> Could
Samuel Wales writes:
> so idk why ff makes emacs not load .emacs or does an xterm.
> /usr/bin/emacs results in indeed emacs25 atm.
>
> gnome and kde are too heavy for my computer, and they can't do
> everything fluxbox can, and fluxbox mostly wfm. i don't get what
> things de's do that i need,
Max Nikulin writes:
>> application/x-shellscript; emacs27 %s; test=test -n "$DISPLAY"
>
> Notice that such entry will be ignored when DISPLAY is not set due to
> specified "test" property. You need to pass X socket and pass or set
> DISPLAY environment to you "headless" container.
Also, note
Craig STCR writes:
> '>$ run-mailcap myscript'
One comment. I do not personally have run-mailcap command on my system,
but searching for its docstring reveals
(http://www.linux-commands-examples.com/run-mailcap):
>> If the mime-type is omitted, an attempt to determine the type is
>> made by
Julien Cubizolles writes:
> org-clock checks for the 'x window-system in order to use the program
> set up by org-clock-x11idle-program-name. Recent Emacs versions use the
> 'pgtk instead of 'x and as such will default to using
> org-emacs-idle-seconds in org-user-idle-seconds.
>
> The following
On Wed, May 25, 2022 at 08:35:19AM +0200, Orm Finnendahl wrote:
> Hi,
>
> Am Dienstag, den 24. Mai 2022 um 19:30:40 Uhr (+0200) schrieb Kepa Diez:
> > (defun focusJump ()
> > (interactive)
> > (if (equal posicion 1)
> > (focusPointInter)
> > (if (equal posicion 2)
> >
Craig STCR writes:
> On 5/20/22 9:44 PM, Ihor Radchenko wrote:
>> However, I am not sure what to do on Windows/Mac.
> Maybe try a quick-and-dirty, cross-platform solution that checks
> non-binary files for a first-line shebang? Could use existing Emacs
> hooks that determine major-mode when
Max Nikulin writes:
> On 24/05/2022 09:51, Timothy wrote:
>>
>> To me, this is another reason for comment and #+attr_X lines not to break
>> paragraphs, as then we can just re-use #+attr_X lines.
>
> I like the idea that comments and attribute lines should not be
> paragraph separators. I
Hi,
Am Dienstag, den 24. Mai 2022 um 19:30:40 Uhr (+0200) schrieb Kepa Diez:
> (defun focusJump ()
> (interactive)
> (if (equal posicion 1)
> (focusPointInter)
> (if (equal posicion 2)
> (focusPointEnd)
> (if (equal posicion 3)
> (focusPointStart)
maybe
Hi all!
I'm keeping a journal of my research activity with org-cite, and
together with citar and vertico, it works great. I have a question
though.
How can I make Org open the PDF file of a resource, using an external
application?
Let me explain: with the point on a org-cite link, pressing C-c
On Wed, May 25, 2022 at 6:53 AM Alessandro Bertulli
wrote:
> How can I make Org open the PDF file of a resource, using an external
> application?
>
> Let me explain: with the point on a org-cite link, pressing C-c C-o asks
> me for the resource to open. Selecting the PDF file opens it with
>
Yeah I was wondering about that 'test' line. I was wondering if, like
you say, it gets ignored. Or if the true / false value gets passed to
some other logic that would, for example, add a '-nw' to the emacs
command line. I have no idea.
On 5/25/22 2:24 AM, Ihor Radchenko wrote:
Max
Appreciate the offer for Saturday, but I have to take care of something on
Saturday. What time slots were you thinking in EDT?
Thanks for this note though, will put this in my notes as well.
On Tue, May 24, 2022, at 9:26 PM, Ihor Radchenko wrote:
> "Samuel Banya" writes:
>
> > Its kind of
Ihor Radchenko writes:
> I think that we might simply allow to define complex configuration
> before the containing paragraph. Something like:
>
> #+attr_latex[name]:
> Vestibulum convallis, lorem blockname_[<>]{text} a tempus semper, dui
> dui euismod elit, vitae placerat urna tortor vitae
On 25/05/2022 21:10, Alessandro Bertulli wrote:
I'm not sure if it's the best way to do so, but it worked for me by
using a lambda:
(setq citar-file-open-function '(lambda (file)
(async-shell-command (format-message "sioyek \"%s\"" file
First of all, it is unsafe. File names
On Wednesday, 25 May 2022 at 16:35, Uwe Brauer wrote:
> Sometimes I only want to convert/export a region or a paragraph of an
> org file to another format, most likely as html or latex.
> I cannot find such a functionality also not in the package system
> does anybody knows about such a function?
On Wed, May 25, 2022 at 11:09 AM Uwe Brauer wrote:
>
> Hi
>
> Sometimes I only want to convert/export a region or a paragraph of an
> org file to another format, most likely as html or latex.
> I cannot find such a functionality also not in the package system
> does anybody knows about such a
>>> "WD" == William Denton writes:
> On 25 May 2022, Uwe Brauer wrote:
>> Sometimes I only want to convert/export a region or a paragraph of an
>> org file to another format, most likely as html or latex.
> Is this different from subtree export? After C-c C-e, C-s will toggle
> "export scope"
On Wed, May 25, 2022 at 11:26 AM Max Nikulin wrote:
>
> On 25/05/2022 21:10, Alessandro Bertulli wrote:
> >
> > I'm not sure if it's the best way to do so, but it worked for me by
> > using a lambda:
> >
> > (setq citar-file-open-function '(lambda (file)
> > (async-shell-command
40 matches
Mail list logo
