From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id aJmPBetWYV8nBwAA0tVLHw (envelope-from ) for ; Wed, 16 Sep 2020 00:06:03 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id MCpgO+pWYV/YJwAAB5/wlQ (envelope-from ) for ; Wed, 16 Sep 2020 00:06:02 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 314FA9401CF for ; Wed, 16 Sep 2020 00:06:02 +0000 (UTC) Received: from localhost ([::1]:38622 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kIKxT-0003KG-LC for larch@yhetil.org; Tue, 15 Sep 2020 20:05:59 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:46676) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kIKwY-0003J5-NK for emacs-orgmode@gnu.org; Tue, 15 Sep 2020 20:05:02 -0400 Received: from mail-pg1-x52b.google.com ([2607:f8b0:4864:20::52b]:41313) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kIKwW-0004Ge-2C for emacs-orgmode@gnu.org; Tue, 15 Sep 2020 20:05:02 -0400 Received: by mail-pg1-x52b.google.com with SMTP id y1so2856646pgk.8 for ; Tue, 15 Sep 2020 17:04:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:subject:in-reply-to:message-id:date :mime-version:content-transfer-encoding; bh=rhiTU5EtQyhFlZPAuuZiSL9gFY7RrAhVbjl/lhNy2F4=; b=HCmqkX9114xsyP5A4SZIfQwr+KOi4ZixHRlcmzpTlsx+WfhZZF0qfGPNaA1Nxmn7re VCTf2ytwqIwj3ugLZzEzHI6fUNfJCIY+VkEmJPUFWNSjXIHvdRSLdXmVXEIitrSzimmS isKq3MxyxlszoXJrTu49hmNLmqD9OaJIcvWmPc9Ba+TMbo7PCgRCpHGpLJABoI4QHjil ABY62zbMwCBLqrOJO/TdvJP1AlhdKxF4gt8ImJW/zdJuA1sb4uPicliOJoIFAFfTdqaG KPejv9IUIutHPztGUfQSmRFTUAeFzrSCbCmBc4lEwUqivsgUKIsq+NYxf6l0P7+1WIO7 thkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:subject :in-reply-to:message-id:date:mime-version:content-transfer-encoding; bh=rhiTU5EtQyhFlZPAuuZiSL9gFY7RrAhVbjl/lhNy2F4=; b=UHRAgJvNIKAoDSOelyU60VQOzbzIsUoCxTUh/3SnRh2oGLwmC93CyihbjXYVI6tA30 CIGNkVjRwtJeGQF+OSij01ZIYDOL6/FVG2LoLl+bcjShOVDXjOaIjrQ+slTddtupzlHA 2tpvRRFSvCKoZ7+XYaFjRX3d/D86k2wafaMrX6dwU8gEu2F7RRCFdW+A/9T3tXdlqe3o 5mISWtCDd5+KY5w4kbBDGnGeNpQyS4Q3C0Y4tpq+MSGoXVMP1LKILrkSAxeyHe4m23gA x+TkWlBp87LMIHmFog3mqBg+0GFyou3EPp7gwXgm42oY04ra79VehNUueWpbU0ZQApIx EfHg== X-Gm-Message-State: AOAM532L2ieqq66WNhbnvVWIucPXuIGMwDluTs25aeZRHqfV8r72oZpt 1qDnZ3IPk2wiPwuNKlp9Komjp6ARZY5r9w== X-Google-Smtp-Source: ABdhPJz3LO8VSkgtITT0ZNfUKU9FhiweBFPyGUI1aY0BMFqXXjh6znL0M1Z0sLZa00nj0yatI2FFtw== X-Received: by 2002:a63:af1d:: with SMTP id w29mr16268994pge.176.1600214697523; Tue, 15 Sep 2020 17:04:57 -0700 (PDT) Received: from tim-desktop (106-69-134-154.dyn.iinet.net.au. [106.69.134.154]) by smtp.gmail.com with ESMTPSA id cf7sm531336pjb.52.2020.09.15.17.04.55 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 15 Sep 2020 17:04:56 -0700 (PDT) References: <87o8m7t5xa.fsf@ebih.ebihd> User-agent: mu4e 1.5.5; emacs 27.1.50 From: Tim Cross To: emacs-orgmode@gnu.org Subject: Re: basic org questions In-reply-to: <87o8m7t5xa.fsf@ebih.ebihd> Message-ID: <87a6xq37tm.fsf@gmail.com> Date: Wed, 16 Sep 2020 10:04:53 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::52b; envelope-from=theophilusx@gmail.com; helo=mail-pg1-x52b.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=HCmqkX91; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.71 X-TUID: 9pjLCzOqtQLr Emanuel Berg via General discussions about Org-mode. writes: > 1) How do I make a region italic? > > This does not fontify and does not show up as > italic type: > > /En g=C3=A5ng i tiden var =C3=A4ven Spanien t=C3=A4ckt av skog. > En gammal ber=C3=A4ttelse menar att man i norra Spanien > kunde hoppa upp p=C3=A5 en apas rygg och ta sig ner till > s=C3=B6dra Spanien utan att kl=C3=A4ttra av en enda g=C3=A5ng. Apan, > underf=C3=B6rst=C3=A5tt, kunde hoppa fr=C3=A5n gren till gren genom > hela halv=C3=B6n. Flyger man =C3=B6ver Spanien idag ser man att > det har g=C3=A5tt =C3=A5t ett och annat tr=C3=A4d sen dess./ > > /This/ works tho. > > 2) How do I have tables not appear centered > by default, but left-aligned? > > 3) How do I have a new paragraph, as indicated by > > p1 > > p2 > > appear w/o indentation, but with a blank line between > p1 and p2 (yes, exactly as stated, really). > It is important to understand the org mode architecture in order to understand how/where to try and change/fix things to get specific results. It is also very important to be clear about this architecture when asking questions so that you can include the most relevant information.=20 Org has a multi-layered architecture. At the top is the org buffer where you put your org text. This text supports markup and other text with special meaning which the Emacs editor will display in specific ways using colours, fonts, overlays etc. When you export an org file, the contents of the org file is extracted and markup, options, 'special' text etc is mapped to the equivalent 'concept' in the back end format. Sometimes, this translation might involve multiple steps (e.g. for PDF the org text is translated into Latex, which is then translated into pdf). Understanding this is critical as all back ends are not the same and sometimes, the changes you need to make need to be performed at the back end rather than within the org file itself. For example, sometimes, a quick and easy change can be achieved by manually editing the *.tex file generated when doing a PDF export and other times, it may be necessary to define a whole new document class in order to achieve the result you want (for example, I defined a new entry for org-latex-classes called 'work' which added additional Latex classes and macro definitions needed to support the format documents had to have for my employer).=20=20 All this means that you need to be explicit when asking a question whether what you want is for the org buffer/file, the exported file and what the exported format is. As with many questions involving technology, you are often better off explaining what your specific outcome is rather than on how to do something as the latter is often asking how to do something to implement what you think is the right solution when in fact a completely different solution might be easier. As an example, with your question about how to make a paragraph italic. Do you want the text to appear italic in the org buffer or do you want the PDF text which results from the export to be italic? Is it actually critical that it is italic or do you just want to make sure that text is rendered in such a way as to make it emphasised or stand out in the final exported output? If it is the latter, I would actually take a completely different approach. Rather than trying to mark the whole paragraph as italic, I would create a quoted block using #+begin_quote/#+end_quote. Each back end will interpret this quoted block in its own way and render it accordingly. Another approach would be to use embedded latex in your document and render the paragraph as a latex block using \begin{em} \end{em} or \begin{it} \end{it} The disadvantage of this approach is that your being very back end specific in your org-file, so exporting to other formats may not work well. With respect to your question regarding table placement in your PDF, have a look at the manual section on exporting and in particular, Latex export options. There are a number of options you can add to your table definition which will affect how the table is rendered or where it is placed within the document. Note that Latex is a VERY powerful document formatting system and it is VERY opinionated. Unlike MS Word and other word processing systems, with Latex derived formatting, your almost always better off leaving Latex to decide how to do things. With Latex, you select a document style and run with that. Tables are notoriously complex to get right and while you can achieve what you want, you will likely need to read up on Latex and how it processes tables and you may need to add or tweak the latex packages included by Org when it generates the output in order to get the precise result you are after. In your current case, you will likely be able to achieve your desired result just using the ':float' or ':placement' commands (see the org manual section on latex export). With respect to your final question on paragraph indent for first line - this is the default style for Latex documents. Different Latex document styles have different paragraph styles, some of which do not indent the first line. You can change the document style by adding a new latex class. For example, many people prefer the Korma Article class for documents over the default Latex Article class. You can change the class in a number of ways including by adding a #+latex_class: header to the org file. e.g. #+latex_class: korma-article Another alternative is to add an additional latex header argument. For example, this may work to disable paragraph indentation #+latex_header: \setlength{\parindent}{0pt} You can also prevent indentation of a specific paragraph by using the latext \noindent command. Note that the above is specific to exports based on Latex (such as PDF export) and will not have effect on other export types. If you really must heavily customise the PDF format, you have the power. However, you will likely need to read up on Latex and the latex to pdf process to understand how that works and then go back to the org manual to work out the best ways to customise org to use the setting you want. The key to success IMO is to be conservative here. Lots of research into typography, text formatting etc has gone into the TeX/LaTeX system and your generally best off going with their style decisions. Look for alternative high-level document styles (such as the Korma, HiTech and other styles) rather than try hacking existing styles as it will be easier and give better results in the long term. HTH Tim --=20 Tim Cross