From: Alain.Cochard@unistra.fr
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Suspected bug with LaTeX export: the pdf does not open
Date: Mon, 20 Aug 2018 18:27:08 +0200 [thread overview]
Message-ID: <23418.60380.333783.437135@frac.u-strasbg.fr> (raw)
In-Reply-To: <87r2itm40h.fsf@alphaville.usersys.redhat.com>
Nick Dokos writes on Mon 20 Aug 2018 11:50:
> [...] you have security problems: the current Fedora is 28, Fedora
> 26 is either end-of-life already or about to be shortly, and Fedora
> 23 is obsolete and possibly dangerous. Please consider upgrading.
Thanks. Yes, 23 is obsolete. But what do you mean "possibly
dangerous"? What are the risks?
In addition to the unexpected problems that regularly occur (to me
anyway) at each distribution change and which take time to fix, I know
-- considering the latest emacs version -- that I have a high risk of
facing a dreadful problem for me (coupling Xfce workspaces and emacs
'other-frame') that I don't even know how to fix. So generally I
"upgrade" when I change my computer. That would be different if there
existed an easy and robust way to downgrade...
Regards
--
EOST (École et Observatoire des Sciences de la Terre)
IPG (Institut de Physique du Globe) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | Fax: +33 (0)3 68 85 01 25
next prev parent reply other threads:[~2018-08-20 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 4:52 Suspected bug with LaTeX export: the pdf does not open Alain.Cochard
2018-08-18 19:34 ` Robert Klein
2018-08-18 20:59 ` Alain.Cochard
2018-08-19 2:31 ` Tim Cross
2018-08-19 4:21 ` Alain.Cochard
2018-09-23 8:41 ` Alain.Cochard
2018-09-24 3:37 ` Alain.Cochard
2018-08-20 15:50 ` Nick Dokos
2018-08-20 16:27 ` Alain.Cochard [this message]
2018-08-20 16:59 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23418.60380.333783.437135@frac.u-strasbg.fr \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).