From: Jean Louis <bugs@gnu.support>
To: Christopher Dimech <dimech@gmx.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Working web links when writing to a dedicated buffer?
Date: Mon, 3 May 2021 02:03:11 +0300 [thread overview]
Message-ID: <YI8vr/zjkWg46kIu@protected.localdomain> (raw)
In-Reply-To: <trinity-e6df88e9-d208-4b01-9fd2-a5dea8ef3d98-1619987148485@3c-app-mailcom-bs08>
* Christopher Dimech <dimech@gmx.com> [2021-05-02 23:26]:
> Is there a way to include working web links when writing to a
> dedicated buffer?
What would that mean? Do you want maybe to expand the text below to
HTML so that link is within <a href? I would use Markdown for
that. Please explain what means to include working web links?
> (defvar gungadin-version-license
> "\nGungadin 1.0 of 2017-05-02\n
> Gungadin is part of Behistun, a Gnu Package.
> Copyright (C) 2017 Christopher Dimech
> Author: Christopher Dimech
>
> Gungadin is Free Software, software that fully respects the
> computing freedom of its users as defined by the Free Software
> Foundation. See `https://www.gnu.org/philosophy/philosophy.html'
>
> You can redistribute exact copies of Gungadin or modify it under
> the terms of the Gnu Affero General Public License as published
> by the Free Software Foundation; either version 3 of the License,
> or (at your option) any later version.")
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/
https://rms-support-letter.github.io/
next prev parent reply other threads:[~2021-05-02 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 20:25 Working web links when writing to a dedicated buffer? Christopher Dimech
2021-05-02 23:03 ` Jean Louis [this message]
2021-05-02 23:25 ` Christopher Dimech
2021-05-03 1:13 ` Jean Louis
2021-05-02 23:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YI8vr/zjkWg46kIu@protected.localdomain \
--to=bugs@gnu.support \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).