emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: Philip.Wong@warwick.ac.uk, 34684@debbugs.gnu.org
Subject: bug#34684: 26.1; Strange characters when inserting date
Date: Thu, 28 Feb 2019 21:56:13 +0200	[thread overview]
Message-ID: <83zhqfit5u.fsf@gnu.org> (raw)
In-Reply-To: <m2zhqf20em.fsf@gmail.com> (message from Robert Pluim on Thu, 28 Feb 2019 20:11:45 +0100)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: "Wong\, Philip" <Philip.Wong@warwick.ac.uk>,  34684@debbugs.gnu.org
> Date: Thu, 28 Feb 2019 20:11:45 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: "Wong, Philip" <Philip.Wong@warwick.ac.uk>
> >> Date: Thu, 28 Feb 2019 14:16:25 +0000
> >> 
> >> When I insert a date by pressing CTRL+C then period then enter I get “<2019-02-28 ¶g¥|>”.
> >> 
> >> I’m not sure what the strange character is (¶g¥|), can someone help?
> >
> > Please show a complete recipe, starting from "emacs -Q", to reproduce
> > the issue.  When I type "Ctrl-C ." in "emacs -Q", Emacs says that
> > sequence is not bound to any command, so I wonder what is needed to
> > "insert a date" in your scenario.
> 
> >From the output, this is 'org-time-stamp', which produces
> <2019-02-28 Thu> here. Based on this in the report:
> 
>     Important settings:
>       value of $LANG: ZHH
>       locale-coding-system: cp1252
> 
> Iʼm assuming thereʼs an issue with buffer-file-coding-system or
> similar.

Unlikely: buffer-file-coding-system has no effect whatsoever on the
text that is inserted into a buffer, it only has effect when you want
to save the buffer or send it to some sub-process.

It could be some snafu in Org, though, e.,g. if it doesn't know how to
support that value of $LANG.  In any case, should be reported to Org
developers first.

  parent reply	other threads:[~2019-02-28 19:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DB7PR01MB41710340234EF2B900832154AF750@DB7PR01MB4171.eurprd01.prod.exchangelabs.com>
2019-02-28 17:55 ` bug#34684: 26.1; Strange characters when inserting date Eli Zaretskii
2019-02-28 19:11   ` Robert Pluim
2019-02-28 19:15     ` Eric Abrahamsen
2019-02-28 19:56     ` Eli Zaretskii [this message]
2019-03-01 10:00       ` Robert Pluim
2019-03-01 10:35         ` Eli Zaretskii
2019-03-01 13:47           ` Robert Pluim
2019-03-01 13:49             ` Robert Pluim
2019-03-01 14:09             ` Eli Zaretskii
2019-03-01 14:25               ` Robert Pluim
2019-03-01 14:42                 ` Eli Zaretskii
2019-03-11  9:41                   ` Wong, Philip
2019-03-11 10:43                     ` Robert Pluim
2019-03-11 10:47                       ` Wong, Philip
2019-03-11 14:58                         ` Eli Zaretskii
     [not found]                           ` <DB7PR01MB4171B6AF4751C4D196E19DECAF480@DB7PR01MB4171.eurprd01.prod.exchangelabs.com>
2019-03-11 16:41                             ` Robert Pluim
2019-03-11 16:43                               ` Wong, Philip
2019-03-11 16:54                                 ` Eli Zaretskii
2019-03-11 16:55                                   ` Wong, Philip
2019-03-11 17:29                                     ` Eli Zaretskii
2019-03-11 17:35                                       ` Wong, Philip
2019-03-11 17:55                                         ` Eli Zaretskii
2019-03-12  9:58                                           ` Wong, Philip
2019-03-12 16:01                                             ` Eli Zaretskii
2019-03-12 16:04                                               ` Wong, Philip
2020-05-22 12:10                                               ` Bastien
2020-05-22 12:18                                                 ` Eli Zaretskii
2019-03-12  3:42                         ` bug#34684: " Takaaki Ishikawa
2019-03-12 15:53                           ` Eli Zaretskii
2019-03-11 14:45                     ` Eli Zaretskii

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=83zhqfit5u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34684@debbugs.gnu.org \
    --cc=Philip.Wong@warwick.ac.uk \
    --cc=rpluim@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).