emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

* [TYPO REPORT] A typo in the Org Manual
@ 2022-09-22  5:30 ika
  2022-09-22  6:50 ` Timothy
  0 siblings, 1 reply; 3+ messages in thread
From: ika @ 2022-09-22  5:30 UTC (permalink / raw)
  To: emacs-orgmode

Greetings,

There seems to be a typo in the Org Manual.

In section 13.8.4: Beamer specific syntax, in the segment showed below,
The `#+END_BEAMER' part does neither run correctly nor makes sense,
The correct code here should be `#+END_EXPORT'.

------------------------
> Insert Beamer-specific code using the following constructs:

>> #+BEAMER: \pause

>> #+BEGIN_EXPORT beamer
>>   Only Beamer export back-end exports this.
>> #+END_BEAMER

>> Text @@beamer:some code@@ within a paragraph.
------------------------

This typo is present on the HTML version of the manual that you could find on the website:

https://orgmode.org/org.html#Beamer-specific-syntax

I'm actually new to mailing-list related development procedure so I'm still learning, but
it might be possible for someone who's proficient in this procedure to quickly fix this
little typo.

Good day for all.
--
ika


^ permalink raw reply	[flat|nested] 3+ messages in thread

• * Re: [TYPO REPORT] A typo in the Org Manual
    2022-09-22  5:30 [TYPO REPORT] A typo in the Org Manual ika
  @ 2022-09-22  6:50 ` Timothy
    2022-09-22 15:54   ` Bastien
    0 siblings, 1 reply; 3+ messages in thread
  From: Timothy @ 2022-09-22  6:50 UTC (permalink / raw)
    To: emacs-orgmode; +Cc: emacs-orgmode
  
  [-- Attachment #1: Type: text/plain, Size: 788 bytes --]
  
  Hi Ika,
  
  > There seems to be a typo in the Org Manual.
  >
  > In section 13.8.4: Beamer specific syntax, in the segment showed below,
  > The `#+END_BEAMER’ part does neither run correctly nor makes sense,
  > The correct code here should be `#+END_EXPORT’.
  
  Thanks for pointing that out, I’ve just pushed a fix in ae2140b1e6bf.
  
  > I’m actually new to mailing-list related development procedure so I’m still learning, but
  > it might be possible for someone who’s proficient in this procedure to quickly fix this
  > little typo.
  
  Thanks for getting in touch! The basics of mailing-list developments is just
  using an email chain issues of issues/PRs, and submitting changes as git patch
  attachments — that’s all there really is to it 🙂
  
  All the best,
  Timothy
  
  ^ permalink raw reply	[flat|nested] 3+ messages in thread

• • * Re: [TYPO REPORT] A typo in the Org Manual
      2022-09-22  6:50 ` Timothy
    @ 2022-09-22 15:54   ` Bastien
      0 siblings, 0 replies; 3+ messages in thread
    From: Bastien @ 2022-09-22 15:54 UTC (permalink / raw)
      To: Timothy; +Cc: emacs-orgmode
    
    Hi Ika,
    
    Timothy <orgmode@tec.tecosaur.net> writes:
    
    > Thanks for getting in touch! The basics of mailing-list developments is just
    > using an email chain issues of issues/PRs, and submitting changes as git patch
    > attachments — that’s all there really is to it 🙂
    
    ... and you can read https://orgmode.org/worg/org-contribute.html for
    even more fun :)
    
    -- 
     Bastien
    
    
    ^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-09-22 17:31 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-22  5:30 [TYPO REPORT] A typo in the Org Manual ika
2022-09-22  6:50 ` Timothy
2022-09-22 15:54   ` Bastien

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).