On Wed, 2025-05-21 at 15:16 -0700, Peter Ehlert wrote:
> > It's not quite the same. What Dan is asking for is that each wiki
> > page should identify when it was updated and for which named
> > release(s) of Debian it is valid. So even if it's out of date it
> >
On 2025-05-22, Jonathan Dowland wrote:
> On Wed May 21, 2025 at 5:01 PM BST, Greg wrote:
>> Why propose yet again the exact thing I proposed upthread (that you
>> required me to spell out with ludicrous explicitness and that you
>> described as unhelpful), as if you've arrived at some epiphany?
>
On Wed May 21, 2025 at 5:01 PM BST, Greg wrote:
Why propose yet again the exact thing I proposed upthread (that you
required me to spell out with ludicrous explicitness and that you
described as unhelpful), as if you've arrived at some epiphany?
What is your problem, anyway?
I didn't think I
ite the same. What Dan is asking for is that each wiki page
should identify when it was updated and for which named release(s) of
Debian it is valid. So even if it's out of date it may be useful to
somebody, or it may be possible to deduce what's wrong for the current
stable in some circums
On 2025-05-20, Jonathan Dowland wrote:
>
> ... I prefer ... the assumption to be that all
> pages applied to the current stable release...
Why propose yet again the exact thing I proposed upthread (that you
required me to spell out with ludicrous explicitness and that you
described as unhelpful),
> 4) You want to rewrite not only the WIKI CONTENT, but the WIKI ENGINE too.
I really appreciate your constructive contributions, thank you.
Stefan
On 2025-05-21, john doe wrote:
Then refrain from prolonging it.
please stop this.
--
John Doe
t actually become obsolete with a new Debian release.
> >The number of incompatible changes in a new release is usually
> >pretty small.
> >
> > 2) Re-creating the *entire* wiki every time there's a new release is
> >a stupidly ridiculous amount
ually
>pretty small.
>
> 2) Re-creating the *entire* wiki every time there's a new release is
>a stupidly ridiculous amount of effort. Not just the initial act
>of moving creating a whole new versioned page for every existing
>nonversioned page -- which
ore amenable to crowdsourcing.
I have multiple problems with this proposal.
1) Most pages don't actually become obsolete with a new Debian release.
The number of incompatible changes in a new release is usually
pretty small.
2) Re-creating the *entire* wiki every time there's
s remain valid and which parts should be
dropped or updated? That's a lot of work, and the whole point of the
wiki is to crowdsource that kind of work from the users of the site, but
that isn't compatible with the need to do it right when a release
takes place.
In contrast my propositio
"Jonathan Dowland" wrote:
> On Tue May 20, 2025 at 4:04 PM BST, Stefan Monnier wrote:
> >> FWIW I didn't find "keep it up to date" useful feedback.
> >
> > Here's my view: replace each current page with a list of "per Debian
> > version" pages. So, when someone edits a page, they don't edit the
On Tue May 20, 2025 at 4:04 PM BST, Stefan Monnier wrote:
FWIW I didn't find "keep it up to date" useful feedback.
Here's my view: replace each current page with a list of "per Debian
version" pages. So, when someone edits a page, they don't edit the
"DebianBootstrap" page, but the "DebianBoot
generally have paid staff. It used to be
they were paid by people buying printed copies; nowadays they're paid
from advertising or subscriptions or whatever. The big exception is
Wikipedia and even that has regular donation campaigns. The Debian wiki
is edited by volunteers, and apart from
On Tue, 20 May 2025 10:56:05 +0100
"Jonathan Dowland" wrote:
> On Mon May 19, 2025 at 2:03 PM BST, Greg wrote:
> > On 2025-05-16, Jonathan Dowland wrote:
> >> On Thu May 15, 2025 at 2:33 PM BST, Dan Ritter wrote:
> >>> The most prominent issue I can see is that there is no unified
> >>> sens
On 2025-05-20, Stefan Monnier wrote:
>> FWIW I didn't find "keep it up to date" useful feedback.
>
> Here's my view: replace each current page with a list of "per Debian
> version" pages. So, when someone edits a page, they don't edit the
> "DebianBootstrap" page, but the "DebianBootstrap/trixie"
don't edit the
> "DebianBootstrap" page, but the "DebianBootstrap/trixie" page.
That sounds like a LOT of extra work for the editors. Asking the
editors to do additional work is probably not a good idea. There's
already a huge shortage of labor/time being put into
> FWIW I didn't find "keep it up to date" useful feedback.
Here's my view: replace each current page with a list of "per Debian
version" pages. So, when someone edits a page, they don't edit the
"DebianBootstrap" page, but the "DebianBootstrap/trixie" page.
The "DebianBootstrap" page would presu
ed to keeping everything current,
> >> so how about having a "last updated" or "last reviewed" date on each
> >> page so people would have an idea of how current that page is.
> >
> > The wiki engine automatically displays a "last modified"
Greg writes:
> The wiki engine automatically displays a "last modified" timestamp
> (it's at the bottom, in the light gray footer box), but you won't
> immediately know whether that update was a major content rewrite, or a
> typo correction.
More useful might be
pdated" or "last reviewed" date on each
>> page so people would have an idea of how current that page is.
>
> The wiki engine automatically displays a "last modified" timestamp (it's
> at the bottom, in the light gray footer box), but you won
gt; page so people would have an idea of how current that page is.
The wiki engine automatically displays a "last modified" timestamp (it's
at the bottom, in the light gray footer box), but you won't immediately
know whether that update was a major content rewrite, or a typo
correction.
On Tue, May 20, 2025 at 9:31 AM Greg wrote:
>
> On 2025-05-20, Jonathan Dowland wrote:
> >>
> >> That's what I said more succinctly. Keep the wikis up to date (I thought
> >> it went without saying "for Debian stable," though there's always a
> >> myriad of ways to be misunderstood but normally on
On 2025-05-20, Jonathan Dowland wrote:
>>
>> That's what I said more succinctly. Keep the wikis up to date (I thought
>> it went without saying "for Debian stable," though there's always a
>> myriad of ways to be misunderstood but normally only one way to be so).
>
> FWIW I didn't find "keep it up
On Mon May 19, 2025 at 2:03 PM BST, Greg wrote:
On 2025-05-16, Jonathan Dowland wrote:
On Thu May 15, 2025 at 2:33 PM BST, Dan Ritter wrote:
The most prominent issue I can see is that there is no unified
sense of chronology. That is, I can look at a page and not have
any idea whether it is cor
o be so).
It's not quite the same. What Dan is asking for is that each wiki page
should identify when it was updated and for which named release(s) of
Debian it is valid. So even if it's out of date it may be useful to
somebody, or it may be possible to deduce what's wrong for the curr
On 2025-05-16, Jonathan Dowland wrote:
> On Thu May 15, 2025 at 2:33 PM BST, Dan Ritter wrote:
>> The most prominent issue I can see is that there is no unified
>> sense of chronology. That is, I can look at a page and not have
>> any idea whether it is correct for current Stable.
That's what I s
On 2025-05-15, Jonathan Dowland wrote:
>
> It's less clear how useful the current wiki is for users. I think many
> of us are inspired by how good the Arch Wiki is for users, and the
> Debian wiki falls far short of that. I guess we should try to improve it
> for user
On 5/15/25 03:52, Jonathan Dowland wrote:
It's less clear how useful the current wiki is for users. I think many
of us are inspired by how good the Arch Wiki is for users, and the
Debian wiki falls far short of that. I guess we should try to improve
it for users, but we don't have
; > are not specific to a distribution, as evidenced by the fact that
> > Debian users often find the Arch wiki useful.
>
> I agree that the Debian Wiki should strive to document
> Debian-specific stuff. I recently deleted (sort-of) the page
> DotFiles¹, after a brief discus
On Thu May 15, 2025 at 2:33 PM BST, Dan Ritter wrote:
The most prominent issue I can see is that there is no unified
sense of chronology. That is, I can look at a page and not have
any idea whether it is correct for current Stable.
Thank you. That is useful feedback, and I agree that we should
On Thu May 15, 2025 at 5:45 PM BST, Stefan Monnier wrote:
one of the problems I see in the world of GNU/Linux is this tendency
to have "per-distribution" documentation for thing which are not
specific to a distribution, as evidenced by the fact that Debian users
often find the Arch w
On 15/05/2025 15:52, Jonathan Dowland wrote:
FYI, some of us have recently re-started an effort to improve the Debian
Wiki. One of the things we need to establish (IMHO) is to determine what
audience the wiki is *for*. For example, it serves a useful function for
Developers, with clusters of
fic to
> a distribution,
+1
> as evidenced by the fact that Debian users often find
> the Arch wiki useful.
> I wish the Arch wiki and Debian wiki (and others, obviously) could
> *share* their effort somehow.
They can, even if the Arch wiki people would not want to cooperate (whi
is good, and
>> although not universally applicable to Debian packages, can be a
>> decent guide.
>
> FYI, some of us have recently re-started an effort to improve the Debian
> Wiki. One of the things we need to establish (IMHO) is to determine what
> audience the wiki is
On Thursday, May 15, 2025 09:33:27 AM Dan Ritter wrote:
> on every single page. The right thing for the Debian Wiki would
> be:
>
> Documentation → Debian 12 Bookworm
> Stable Version: 12 Bookworm
> Long Term Support Version: 11 Bullseye
> Unsupported Versions: 10 / 9 / 8 /
Jonathan Dowland wrote:
> FYI, some of us have recently re-started an effort to improve the Debian
> Wiki. One of the things we need to establish (IMHO) is to determine what
> audience the wiki is *for*. For example, it serves a useful function for
> Developers, with clusters
be a
decent guide.
FYI, some of us have recently re-started an effort to improve the Debian
Wiki. One of the things we need to establish (IMHO) is to determine what
audience the wiki is *for*. For example, it serves a useful function for
Developers, with clusters of pages for Debconfs, summers of
to...@tuxteam.de wrote:
>On Tue, Dec 03, 2024 at 12:17:22PM -0500, Jeffrey Walton wrote:
>> Hi Everyone,
>>
>> Does anyone know which Debian mailing list should be used for wiki
>> discussions?
>>
>> Here are some resources, but I cannot find contact info
On Tue, Dec 03, 2024 at 08:37:24PM +0100, to...@tuxteam.de wrote:
> On Tue, Dec 03, 2024 at 12:17:22PM -0500, Jeffrey Walton wrote:
> > Hi Everyone,
> >
> > Does anyone know which Debian mailing list should be used for wiki
> > discussions?
> >
> > Her
On Tue, Dec 03, 2024 at 12:17:22PM -0500, Jeffrey Walton wrote:
> Hi Everyone,
>
> Does anyone know which Debian mailing list should be used for wiki
> discussions?
>
> Here are some resources, but I cannot find contact info or a mailing list.
>
>* List
Hi Everyone,
Does anyone know which Debian mailing list should be used for wiki discussions?
Here are some resources, but I cannot find contact info or a mailing list.
* List of mailing lists: <https://lists.debian.org/completeindex.html>
* Debian wiki: <https://wiki.d
debian-u...@howorth.org.uk wrote:
>Franco Martelli wrote:
>> On 25/07/24 at 15:07, Greg Wooledge wrote:
>> > Yeah... I have to use a Private window (Firefox) or an Incognito
>> > window (Chrome) to duplicate this. If I'm using my regular browser
>> > se
Franco Martelli wrote:
> On 25/07/24 at 15:07, Greg Wooledge wrote:
> > Yeah... I have to use a Private window (Firefox) or an Incognito
> > window (Chrome) to duplicate this. If I'm using my regular browser
> > sessions where I'm logged in to the wiki, I don'
On 25/07/24 at 15:07, Greg Wooledge wrote:
Yeah... I have to use a Private window (Firefox) or an Incognito window
(Chrome) to duplicate this. If I'm using my regular browser sessions
where I'm logged in to the wiki, I don't get that result.
When in editing mode by clicking &
ome) to duplicate this. If I'm using my regular browser sessions
where I'm logged in to the wiki, I don't get that result.
On 25/07/2024 19:11, Greg Wooledge wrote:
On Thu, Jul 25, 2024 at 18:54:38 +0700, Max Nikulin wrote:
https://wiki.debian.org/EnvironmentVariables?action=recall&rev=32
[...]
I can't quite guess what "text has no left margin" means here.
Firefox-115, see the attachment. Notice that "General",
looks fine, while some of you are seeing... I don't know what. I can't
quite guess what "text has no left margin" means here.
Oh -- if I do it in a Chrome Incognito window, I get different results.
So, I guess being logged in to the wiki changes the HTML just enough to
work a
On 25/07/2024 10:42, Greg Wooledge wrote:
On Thu, Jul 25, 2024 at 09:50:43 +0700, Max Nikulin wrote:
https://wiki.debian.org/EnvironmentVariables?action=raw&rev=33
has one empty line after "<>" while rev=22 has 2 empty
lines and it may be more significant than a space before "<<".
I assume y
s article has an extra space in the translations line causing
> extra indentation due to rather weird markup
>
>
I don't touch the translation stuff. Whatever the Debian translation team
wants to do, I let them do it. If the wiki markup for the translations
table is broken, someone
On 25/07/2024 02:05, Franco Martelli wrote:
I'm using firefox-esr version: 115.13.0esr-1~deb12u1
Here I see the TOC not indented (no space before << tag):
https://wiki.debian.org/EnvironmentVariables?action=raw
Here instead I see the TOC indented (a space before << tag):
https://wiki.debian.org
On 24/07/24 at 20:15, Greg Wooledge wrote:
https://wiki.debian.org/Permissions?action=raw
here there's a space before the << tag and, as I said, clicking on the
"Preview" button when in edit mode, it didn't help.
Well, the table of contents is indented on that page as well.
It sounds like you'
On Wed, Jul 24, 2024 at 20:08:08 +0200, Franco Martelli wrote:
> On 24/07/24 at 15:34, Greg Wooledge wrote:
> > > Could anybody tell me what I did wrong?
> > You had a leading space before the << tag. That caused the TOC to be
> > indented. I removed that.
>
> Oh, Thank you very much Greg, what
On 24/07/24 at 15:34, Greg Wooledge wrote:
Could anybody tell me what I did wrong?
You had a leading space before the << tag. That caused the TOC to be
indented. I removed that.
Oh, Thank you very much Greg, what confused me it was the page that I
took as reference:
https://wiki.debian.or
On Wed, Jul 24, 2024 at 15:19:29 +0200, Franco Martelli wrote:
> https://wiki.debian.org/EnvironmentVariables
>
> The trouble is that the page has lost indentation, the text begins on the
> left side of the page.
The only part that was indented was the table of contents itself. I
fixed that.
>
Hi,
I've added <> (the index of all paragraphs inside
the wiki page) directive to this wiki page:
https://wiki.debian.org/EnvironmentVariables
The trouble is that the page has lost indentation, the text begins on
the left side of the page.
In addition when I'm in editing
better for that purpose.
For most purposes, it is better to use LOGNAME, precisely because
this lets the user specify the value.
The following man page is explicitly linked from the wiki page
environ(7) § NOTES:
The HOME, LOGNAME, SHELL, and USER variables are set when the user is
change
On Mon, Mar 25, 2024 at 08:48:04PM +0100, Patrice Duroux wrote:
> Hi,
>
> 1. Using CodeSearch, it is not clear to me when to use one or the other.
Your original Subject: header mentions $USER and $LOGNAME so I assume
you're asking about these.
$LOGNAME is the standard variable which is set by th
Hi,
1. Using CodeSearch, it is not clear to me when to use one or the other.
2. Would it be nice if the EnvironmentVariables page were linked to a
new page named EnvironmentVariablesList (the same way as DotFiles and
DotFilesList)?
Best,
Patrice
On Tue, 5 Mar 2024, Greg Wooledge wrote:
> On Tue, Mar 05, 2024 at 11:23:59AM -0500, Paul M Foster wrote:
>> On Tue, Mar 05, 2024 at 04:15:20PM +, fxkl4...@protonmail.com wrote:
>>
>>> how do i access the debian wiki
>>> https://wiki.debian.org/
>>>
On Tue, Mar 05, 2024 at 11:23:59AM -0500, Paul M Foster wrote:
> On Tue, Mar 05, 2024 at 04:15:20PM +, fxkl4...@protonmail.com wrote:
>
> > how do i access the debian wiki
> > https://wiki.debian.org/
> > all i get is
> >
> >
> >
> >
>
On Tue, 5 Mar 2024, Greg Wooledge wrote:
> On Tue, Mar 05, 2024 at 04:15:20PM +, fxkl4...@protonmail.com wrote:
>> how do i access the debian wiki
>> https://wiki.debian.org/
>> all i get is
>>
>>
>>
>>
>> Forbidden
>>
>> You are
On Tue, Mar 05, 2024 at 04:15:20PM +, fxkl4...@protonmail.com wrote:
> how do i access the debian wiki
> https://wiki.debian.org/
> all i get is
>
>
>
>
> Forbidden
>
> You are not allowed to access this!
>
Check your firewall, proxies or other items
On Tue, Mar 05, 2024 at 04:15:20PM +, fxkl4...@protonmail.com wrote:
> how do i access the debian wiki
> https://wiki.debian.org/
> all i get is
>
>
>
>
> Forbidden
>
> You are not allowed to access this!
>From <https://wiki.debian.org/DebianWiki/FAQ
Am 05.03.2024 um 16:15:20 Uhr schrieb fxkl4...@protonmail.com:
> how do i access the debian wiki
> https://wiki.debian.org/
> all i get is
Works for me.
--
Gruß
Marco
Send spam to 1709651720mu...@cartoonies.org
how do i access the debian wiki
https://wiki.debian.org/
all i get is
Forbidden
You are not allowed to access this!
g...@wooledge.org wrote:
>On Sat, Aug 26, 2023 at 07:40:46AM -0500, Nate Bargmann wrote:
>>
>> I was able to successfully change my password and update my Wiki home
>> page a little while ago. It has been a long time since I created the
>> account and don't
Snapd. That is going to cause
> trouble for users who remove Snapd, and still use *.deb packages. I
> expect some users will want to move from the other distro to Debian.
>
> Two of the wiki articles that will help with a migration to Debian are
> <https://wiki.debian.org/Gnome&
dated since
it's last edit on December 24,2019
Who does that?
You do. That's what a wiki is.
"Account creation failed: Automatic account creation disabled to stop
spammers signing up. Please contact w...@debian.org and describe what
you want to do in the wiki. Please contact us i
* On 2023 26 Aug 07:57 -0500, Greg Wooledge wrote:
> On Sat, Aug 26, 2023 at 07:40:46AM -0500, Nate Bargmann wrote:
> > * On 2023 26 Aug 07:13 -0500, Anssi Saari wrote:
> > > Nate Bargmann writes:
> > >
> > > > This Wiki is semi-private in that editing i
On Sat, Aug 26, 2023 at 10:29:02AM -0400, Jeffrey Walton wrote:
> On Sat, Aug 26, 2023 at 10:15 AM Dan Ritter wrote:
[...]
> > The basic problem with popcon is that it is opt-in, and nobody
> > who is at all privacy conscious opts-in.
> >
> > (I fully support this decision. It is absolutely corr
On Sat, Aug 26, 2023 at 10:15 AM Dan Ritter wrote:
>
> Jeffrey Walton wrote:
> > Popularity Contest (https://popcon.debian.org/) would be good to
> > consult. But it looks like something is sideways. It does not provide
> > usage statistics for packages like kde-full and gnome. I'm getting the
> >
er 24,2019
Who does that?
You do. That's what a wiki is.
"Account creation failed: Automatic account creation disabled to stop
spammers signing up. Please contact w...@debian.org and describe what
you want to do in the wiki. Please contact us in English, otherwise we
will have to
On Sat, Aug 26, 2023 at 07:40:46AM -0500, Nate Bargmann wrote:
> * On 2023 26 Aug 07:13 -0500, Anssi Saari wrote:
> > Nate Bargmann writes:
> >
> > > This Wiki is semi-private in that editing is not open to just everyone
> > > but may only be done through an a
* On 2023 26 Aug 07:13 -0500, Anssi Saari wrote:
> Nate Bargmann writes:
>
> > This Wiki is semi-private in that editing is not open to just everyone
> > but may only be done through an account (apparently I have one and now
> > have to figure out how to reset my passwor
Nate Bargmann writes:
> This Wiki is semi-private in that editing is not open to just everyone
> but may only be done through an account (apparently I have one and now
> have to figure out how to reset my password).
Good for you. I tried creating an account but after putting in name
* On 2023 25 Aug 23:57 -0500, Jeffrey Walton wrote:
> On Fri, Aug 25, 2023 at 3:50 PM Greg Wooledge wrote:
> >
> > On Fri, Aug 25, 2023 at 01:26:29PM -0400, Jeffrey Walton wrote:
> > > Two of the wiki articles that will help with a migration to Debian are
> > > &l
On Sat, 2023-08-26 at 00:55 -0400, Jeffrey Walton wrote:
> I'm getting the
> message, "No Popularity contest entry for kde-full" (and friends). I
> use kde-full and I have popularity contest enabled, so there should be
> at least one entry.
Perhaps because they're metapackages?
--
Tixy
On Fri, Aug 25, 2023 at 3:50 PM Greg Wooledge wrote:
>
> On Fri, Aug 25, 2023 at 01:26:29PM -0400, Jeffrey Walton wrote:
> > Two of the wiki articles that will help with a migration to Debian are
> > <https://wiki.debian.org/Gnome> and <https://wiki.debian.org/KDE>.
er 24,2019
Who does that?
You do. That's what a wiki is.
:)
..
Bret Busby
Armadale
West Australia
(UTC+0800)
..
does that?
You do. That's what a wiki is.
On August 25, 2023 12:49:44 PM Greg Wooledge wrote:
On Fri, Aug 25, 2023 at 01:26:29PM -0400, Jeffrey Walton wrote:
Two of the wiki articles that will help with a migration to Debian are
<https://wiki.debian.org/Gnome> and <https://wiki.debian.org/KDE>.
It would be helpful i
On Fri, Aug 25, 2023 at 01:26:29PM -0400, Jeffrey Walton wrote:
> Two of the wiki articles that will help with a migration to Debian are
> <https://wiki.debian.org/Gnome> and <https://wiki.debian.org/KDE>.
>
> It would be helpful if folks with Gnome and KDE experien
wiki articles that will help with a migration to Debian are
<https://wiki.debian.org/Gnome> and <https://wiki.debian.org/KDE>.
It would be helpful if folks with Gnome and KDE experience would look
over the articles and provide corrections and updates.
Jeff
On Tue, Aug 22, 2023 at 05:02:22PM -0400, Oliver Wenston wrote:
> I purchased a vps to use as my vpn server, and found out that it was black
> listed from the https://wiki.debian.org/ website. I am currently using
> Bookworm, and would love to be able to visit the wiki with my vpn.
>
Dear Debian mailing list,
I purchased a vps to use as my vpn server, and found out that it was black
listed from the https://wiki.debian.org/ website. I am currently using
Bookworm, and would love to be able to visit the wiki with my vpn.
Who should I contact next on a private channel to get my
From: Me
Date: Thu, 15 Jun 2023 19:23:26 +0200
Message-id: <[🔎] 568e7aa9-e061-194a-13f8-8e2379f69...@nodatagrabbing.com>
In-reply-to: <[🔎]
caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
References: <[🔎]
caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
and
Hi,
15 juin 2023, 20:15 de m...@nodatagrabbing.com:
> Although I have never used it myself (I am 100% a vim and by extension a
> vimwiki person)
>
+1 for vimwiki.
> I know someone who used (not sure if he still does) Basket Notes
> (https://basket-notepads.github.io/) and loves it.
>
In that ca
On 2023-06-15 12:54, Susmita/Rajib wrote:
My dear illustrious Leaders of the Debian-user List and Senior List Members,
There is Wiki.js but a Debian package for wiki.js isn't available.
Then there is libreoffice-wiki-publisher in Debian, the LibreOffice
extension for working with Medi
vofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
>
> [ ... ]
> > emacs ?
>
> Thank you, Mr. Verdier, for replying to my post.
>
> So far as I am aware, text editors like Gedit, Vim, Emacs, Sublime
> Text, et al, will not provide a WYSIWYG editing experien
... ]
> emacs ?
Thank you, Mr. Verdier, for replying to my post.
So far as I am aware, text editors like Gedit, Vim, Emacs, Sublime
Text, et al, will not provide a WYSIWYG editing experience like a
word processor. One'll need to manually apply the wiki formatting tags
to achieve the
On Thu, 2023-06-15 at 13:54 +0200, Michel Verdier wrote:
> On 2023-06-15, Susmita/Rajib wrote:
>
> > I require a WYSIWYG editor. Zim is one. But I also need another
> > supporting editor to further polish up files.
>
> emacs ?
>
+1; emacs is good! Also i use emacs very heavy ^^^
Sincerely,
-
On 2023-06-15, Susmita/Rajib wrote:
> I require a WYSIWYG editor. Zim is one. But I also need another
> supporting editor to further polish up files.
emacs ?
My dear illustrious Leaders of the Debian-user List and Senior List Members,
There is Wiki.js but a Debian package for wiki.js isn't available.
Then there is libreoffice-wiki-publisher in Debian, the LibreOffice
extension for working with MediaWiki articles.
But files created with zim
On 1/10/23 13:12, Dan Ritter wrote:
Georgi Naplatanov wrote:
Hi all!
I've just read Debian's Wiki page about CPU Microcode and there are
mentioned Intel's and AMD's processors for AMD64 architecture.
What is the situation with processors from other architectures
(arm64
Georgi Naplatanov wrote:
> Hi all!
>
> I've just read Debian's Wiki page about CPU Microcode and there are
> mentioned Intel's and AMD's processors for AMD64 architecture.
>
> What is the situation with processors from other architectures
> (arm64/A
Hi all!
I've just read Debian's Wiki page about CPU Microcode and there are
mentioned Intel's and AMD's processors for AMD64 architecture.
What is the situation with processors from other architectures
(arm64/AArch64 for example)?
- do they have microcode?
- can micr
On Thu, 1 Dec 2022 22:03:16 +0100
Yvan Masson wrote:
> I made a few modifications based on your comments:
> https://wiki.debian.org/GRUB2?action=diff&rev2=28&rev1=27
>
> Hope it is clear now.
Much better, thank you.
--
Does anybody read signatures any more?
https://charlescurley.com
https:/
Le 01/12/2022 à 18:14, Charles Curley a écrit :
On Thu, 1 Dec 2022 16:07:53 +0100
Yvan Masson wrote:
I have just updated the GRUB2 page on the wiki to briefly explain how
GRUB2 should be configured in case of software RAID [1]. As I am not
an expert nor an English native, could someone have a
1 - 100 of 425 matches
Mail list logo
