From: Bastien <bzg@altern.org>
To: Sanjib Sikder <sanjibju2002@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Line breaking problem in Description List
Date: Fri, 28 Dec 2012 09:58:29 +0100 [thread overview]
Message-ID: <87bode4kp6.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAL1SgUp7rD0s-LAgEmndEF-JX9HCUqc6xcw0pmDtKH3+Z06rBw@mail.gmail.com> (Sanjib Sikder's message of "Thu, 27 Dec 2012 00:47:50 +0530")
Hi Sanjib,
Sanjib Sikder <sanjibju2002@gmail.com> writes:
> Can anyone look into the issue please ?
Please wait for one week before "pinging" the list for a reply.
Doing otherwise sends useless emails to the >1400 subscribers
of the list.
Thanks!
--
Bastien
prev parent reply other threads:[~2012-12-28 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 9:12 Line breaking problem in Description List Sanjib Sikder
2012-12-26 19:17 ` Sanjib Sikder
2012-12-26 20:16 ` Thomas S. Dye
2012-12-27 8:21 ` Sanjib Sikder
2012-12-28 8:58 ` Bastien [this message]
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=87bode4kp6.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=sanjibju2002@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).