Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #70879 > unrolled thread

I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without

Back to article view | Back to comp.os.linux.misc

Contents

  I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-13 01:16 +0000
    Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without rbowman <bowman@montana.com> - 2025-08-13 02:40 +0000
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-08-13 08:57 -0400
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Jason H <jason_hindle@yahoo.com> - 2025-08-14 21:05 +0000
        Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without rbowman <bowman@montana.com> - 2025-08-15 08:37 +0000
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without John Ames <commodorejohn@gmail.com> - 2025-08-15 08:13 -0700
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-08-15 18:26 +0000
              Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-15 22:37 +0000
                Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-08-16 00:43 +0000
                  Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-16 02:10 +0000
    Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-08-13 08:53 -0400
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Nuno Silva <nunojsilva@invalid.invalid> - 2025-08-14 00:45 +0100
        Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without rbowman <bowman@montana.com> - 2025-08-14 01:09 +0000
    Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-08-13 11:01 -0400
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E. R." <robin_listas@es.invalid> - 2025-08-13 17:16 +0200
        Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-08-16 08:27 +0000
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-16 08:32 +0000
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without The Natural Philosopher <tnp@invalid.invalid> - 2025-08-13 17:31 +0100
        Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-13 21:30 +0000
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Allodoxaphobia <trepidation@example.net> - 2025-08-13 19:48 +0000
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without rbowman <bowman@montana.com> - 2025-08-13 20:10 +0000
    Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-08-13 19:34 +0000
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-13 21:31 +0000
        Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E. R." <robin_listas@es.invalid> - 2025-08-13 23:40 +0200
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-13 23:42 +0000
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without rbowman <bowman@montana.com> - 2025-08-14 01:08 +0000
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E. R." <robin_listas@es.invalid> - 2025-08-14 10:51 +0200
              Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-14 08:53 +0000
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-08-14 01:30 +0000
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without rbowman <bowman@montana.com> - 2025-08-14 01:05 +0000
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Rene Kita <mail@rkta.de> - 2025-08-15 04:55 +0000
        Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-15 05:38 +0000
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Rene Kita <mail@rkta.de> - 2025-08-20 05:54 +0000
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-08-16 08:33 +0000
        Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Rich <rich@example.invalid> - 2025-08-16 18:28 +0000
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-08-16 19:05 +0000
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without The Natural Philosopher <tnp@invalid.invalid> - 2025-08-16 21:08 +0100
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-08-16 20:38 +0000
              Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-17 00:38 +0000
                Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Nuno Silva <nunojsilva@invalid.invalid> - 2025-08-17 09:08 +0100
                Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-08-17 09:16 +0000
                  Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-17 22:27 +0000
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Richard Kettlewell <invalid@invalid.invalid> - 2025-08-16 22:27 +0100
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-17 00:44 +0000
              Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Nuno Silva <nunojsilva@invalid.invalid> - 2025-08-17 09:02 +0100
                Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Richard Kettlewell <invalid@invalid.invalid> - 2025-08-18 08:31 +0100
                  Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-18 08:21 +0000
                  Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Nuno Silva <nunojsilva@invalid.invalid> - 2025-08-22 10:18 +0100
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E.R." <robin_listas@es.invalid> - 2025-08-19 12:06 +0200
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 00:50 +0000
              Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E.R." <robin_listas@es.invalid> - 2025-08-20 12:20 +0200
                Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 22:16 +0000
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-08-23 12:22 +0000
              Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E.R." <robin_listas@es.invalid> - 2025-08-24 00:38 +0200
                Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-08-24 11:15 +0000
                  Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E.R." <robin_listas@es.invalid> - 2025-08-24 22:44 +0200
                  Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-24 22:16 +0000
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> - 2025-08-21 11:44 +0300
    Re: I?m A Linux Expert, And Here Are 6 Commands I Can?t Live Without John McCue <jmclnx@gmail.com.invalid> - 2025-08-13 21:05 +0000
    Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> - 2025-08-14 14:50 +0300
      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-14 22:45 +0000
        Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-08-16 00:20 +0000
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-16 02:07 +0000
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-08-19 13:40 +0000
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without rbowman <bowman@montana.com> - 2025-08-16 09:47 +0000
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-08-16 17:04 +0000
              Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-17 00:45 +0000
                Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without rbowman <bowman@montana.com> - 2025-08-17 07:20 +0000
              Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without rbowman <bowman@montana.com> - 2025-08-17 07:18 +0000
          Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E.R." <robin_listas@es.invalid> - 2025-08-19 12:28 +0200
            Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 00:59 +0000
              Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E.R." <robin_listas@es.invalid> - 2025-08-20 12:32 +0200
                Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 22:21 +0000
                  Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E.R." <robin_listas@es.invalid> - 2025-08-21 02:29 +0200
                    Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-21 01:29 +0000
                      Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without "Carlos E.R." <robin_listas@es.invalid> - 2025-08-21 12:46 +0200
    Re: I’m A Linux Expert, And Here Are 6 Commands I Can’t Live Without Jason H <jason_hindle@yahoo.com> - 2025-08-14 21:07 +0000

Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →

#71482

Le 17-08-2025, Lawrence D’Oliveiro <ldo@nz.invalid> a écrit :
> On 16 Aug 2025 20:38:51 GMT, Stéphane CARPENTIER wrote:
>
>> On 2025-08-16, Rich <rich@example.invalid> wrote:
>>
>>> The unified output (-u option) provides a 'diff' view that is much
>>> more ameniable to being understood by humans.
>> 
>> I'm not impressed by the difference.
>
> By displaying the common lines just once, as surrounding context, the “-u” 
> format provides cues so a tool like patch(1) can find the place in the 
> file to substitute the old lines with the new ones. Not relying on strict 
> line numbers to find the place is the secret to how patch is (usually) 
> able to do its work on a file that already has patches applied from other 
> sources.

I know what the differences are and what they are for. I mean, It's far
from enough to make me switch from vimdiff/nvim -d to diff. 

> This facility for merging patches from multiple sources is the foundation 
> on which open-source development collaboration is built.

I'm speaking about reading the output. Of course, long ago, sending only
patches like that was the easier way. Now, with git, it's done behind
the hood.

-- 
Si vous avez du temps à perdre :
https://scarpet42.gitlab.io

[toc] | [prev] | [next] | [standalone]

#71533

On 17 Aug 2025 09:16:46 GMT, Stéphane CARPENTIER wrote:

> Le 17-08-2025, Lawrence D’Oliveiro <ldo@nz.invalid> a écrit :
>>
>> On 16 Aug 2025 20:38:51 GMT, Stéphane CARPENTIER wrote:
>>
>>> On 2025-08-16, Rich <rich@example.invalid> wrote:
>>>
>>>> The unified output (-u option) provides a 'diff' view that is
>>>> much more ameniable to being understood by humans.
>>>
>>> I'm not impressed by the difference.
>>
>> By displaying the common lines just once, as surrounding context,
>> the “-u” format provides cues so a tool like patch(1) can find the
>> place in the file to substitute the old lines with the new ones.
>> Not relying on strict line numbers to find the place is the secret
>> to how patch is (usually) able to do its work on a file that
>> already has patches applied from other sources.
>
> I know what the differences are and what they are for. I mean, It's
> far from enough to make me switch from vimdiff/nvim -d to diff.

What you’ve got there is some kind of in-editor facility for showing
differences, which is all very well, but not relevant to the issue of
patch submission.

>> This facility for merging patches from multiple sources is the
>> foundation on which open-source development collaboration is built.
>
> I'm speaking about reading the output. Of course, long ago, sending
> only patches like that was the easier way. Now, with git, it's done
> behind the hood.

I’m not sure what you mean by “behind the hood”. When you use commands
like “git diff”, “git format-patch” and “git apply”, these are all
displaying and accepting patches in unified-diff format.

In short, Git works by subsuming the functionality of patch(1) into
its very core.

[toc] | [prev] | [next] | [standalone]

#71417

Rich <rich@example.invalid> writes:
> Stéphane CARPENTIER <sc@fiat-linux.fr> wrote:
>> I never use "diff". I really don't like the way it's displayed. I'm using
>> "vimdiff" or "nvim -d" a lot, because at the same time it's easier to
>> see what I want and it's easier to make the right changes.
>
> diff's default output is an 'ed script' which is not very human 
> readable at all.

That’s not correct.

    richard@tsais:~$ diff a b
    1c1
    < aaa
    ---
    > bbb
    richard@tsais:~$ diff --ed a b
    1c
    bbb
    .

(Although agreed that neither are sensible options for human
consumption.)

-- 
https://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#71424

On Sat, 16 Aug 2025 22:27:02 +0100, Richard Kettlewell wrote:

> (Although agreed that neither are sensible options for human
> consumption.)

I remember many decades ago one or two open-source projects specifying 
that they wanted patches supplied in context-diff format. Nowadays 
unified-diff is just about universal.

I had to recheck “info diff” (the man page being insufficient in this 
case) to refresh my memory of what context-diff looked like; I would agree 
with the vast majority of open-source software developers, that unified-
diff is preferable.

[toc] | [prev] | [next] | [standalone]

#71472

On 2025-08-17, Lawrence D’Oliveiro wrote:

> On Sat, 16 Aug 2025 22:27:02 +0100, Richard Kettlewell wrote:
>
>> (Although agreed that neither are sensible options for human
>> consumption.)
>
> I remember many decades ago one or two open-source projects specifying 
> that they wanted patches supplied in context-diff format. Nowadays 
> unified-diff is just about universal.
>
> I had to recheck “info diff” (the man page being insufficient in this 
> case) to refresh my memory of what context-diff looked like; I would agree 
> with the vast majority of open-source software developers, that unified-
> diff is preferable.

It's nice to have both formats (besides the others; and also, unified
output can be configured to have even more lines of context).

While unified output is usually convenient because of the context, there
will be times where I really just want the changes (i.e. when the
context *is* visual clutter), then the default output of GNU diff suits
me better.


BTW, is it just lack of coffee or both the online manual page and the
GNU info manual section for GNU diff do not explain/specify the default
output format? (Compare with IEEE 1003.1 [1].)

[1] https://pubs.opengroup.org/onlinepubs/9799919799/utilities/diff.html

-- 
Nuno Silva

[toc] | [prev] | [next] | [standalone]

#71555

Nuno Silva <nunojsilva@invalid.invalid> writes:
> BTW, is it just lack of coffee or both the online manual page and the
> GNU info manual section for GNU diff do not explain/specify the default
> output format? (Compare with IEEE 1003.1 [1].)
>
> [1] https://pubs.opengroup.org/onlinepubs/9799919799/utilities/diff.html

The man page is little more than an option summary. The texinfo manual
describes the default output format here:

https://www.gnu.org/software/diffutils/manual/html_node/Detailed-Normal.html

-- 
https://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#71556

On Mon, 18 Aug 2025 08:31:03 +0100, Richard Kettlewell wrote:

> On Sun, 17 Aug 2025 00:44:26 -0000 (UTC), Lawrence D’Oliveiro wrote:
>
>> I had to recheck “info diff” (the man page being insufficient in
>> this case) to refresh my memory of what context-diff looked like; I
>> would agree with the vast majority of open-source software
>> developers, that unified-diff is preferable.
>>
> The man page is little more than an option summary. The texinfo
> manual describes the default output format here:
>
> https://www.gnu.org/software/diffutils/manual/html_node/Detailed-Normal.html

So I noticed.

[toc] | [prev] | [next] | [standalone]

#71900

On 2025-08-18, Richard Kettlewell wrote:

> Nuno Silva <nunojsilva@invalid.invalid> writes:
>> BTW, is it just lack of coffee or both the online manual page and the
>> GNU info manual section for GNU diff do not explain/specify the default
>> output format? (Compare with IEEE 1003.1 [1].)
>>
>> [1] https://pubs.opengroup.org/onlinepubs/9799919799/utilities/diff.html
>
> The man page is little more than an option summary. The texinfo manual
> describes the default output format here:
>
> https://www.gnu.org/software/diffutils/manual/html_node/Detailed-Normal.html

Thanks, that eluded me when I was looking at it, either I failed at
searching, or I didn't search further because I assumed it was the
coreutils info manual (hence why I mentioned "section"). It is indeed
documented there :-)

-- 
Nuno Silva

[toc] | [prev] | [next] | [standalone]

#71640

On 2025-08-16 20:28, Rich wrote:
> Stéphane CARPENTIER <sc@fiat-linux.fr> wrote:
>> I never use "diff". I really don't like the way it's displayed. I'm using
>> "vimdiff" or "nvim -d" a lot, because at the same time it's easier to
>> see what I want and it's easier to make the right changes.
> 
> diff's default output is an 'ed script' which is not very human
> readable at all.
> 
> The unified output (-u option) provides a 'diff' view that is much more
> ameniable to being understood by humans.
> 

diff --side-by-side --suppress-common-lines --ignore-space-change \
    $1 $2 | less -S


But lately what I use is "meld".

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#71694

On Tue, 19 Aug 2025 12:06:04 +0200, Carlos E.R. wrote:

> But lately what I use is "meld".

<https://meldmerge.org/> -- seems to do a lot.

[toc] | [prev] | [next] | [standalone]

#71743

On 2025-08-20 02:50, Lawrence D’Oliveiro wrote:
> On Tue, 19 Aug 2025 12:06:04 +0200, Carlos E.R. wrote:
> 
>> But lately what I use is "meld".
> 
> <https://meldmerge.org/> -- seems to do a lot.

For example, after an update an rpm based system there are a lot of 
.rpmold or .rpmorig files. I compare the config files with the other 
version and easily copy over the new or the old lines into the active file.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#71795

On Wed, 20 Aug 2025 12:20:37 +0200, Carlos E.R. wrote:

> For example, after an update an rpm based system there are a lot of
> .rpmold or .rpmorig files. I compare the config files with the other
> version and easily copy over the new or the old lines into the
> active file.

On Debian with a package upgrade, if the config file from the old
package hasn’t been changed from the default, it quietly replaces it
with the version from the new package. If it has been changed, then it
prompts you to ask what to do.

So only in the latter case do you end up with leftover configs from
the old version.

[toc] | [prev] | [next] | [standalone]

#72038

Le 19-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit :
> On 2025-08-16 20:28, Rich wrote:
>> Stéphane CARPENTIER <sc@fiat-linux.fr> wrote:
>>> I never use "diff". I really don't like the way it's displayed. I'm using
>>> "vimdiff" or "nvim -d" a lot, because at the same time it's easier to
>>> see what I want and it's easier to make the right changes.
>> 
>> diff's default output is an 'ed script' which is not very human
>> readable at all.
>> 
>> The unified output (-u option) provides a 'diff' view that is much more
>> ameniable to being understood by humans.
>> 
>
> diff --side-by-side --suppress-common-lines --ignore-space-change \
>     $1 $2 | less -S

I'm still not convinced. OK, it's a little bit better to read than the
default. But it's still very poor compared with vimdiff/nvim -d. And,
unlike vim/neovim, it's still useless to report some change in a file to
another file.

> But lately what I use is "meld".

OK, I looked at it a little bit, it's the same information level than
vimdiff/nvim -v. But it looks more mouse driven than keyboard driven and
I'd have to learn something new.

-- 
Si vous avez du temps à perdre :
https://scarpet42.gitlab.io

[toc] | [prev] | [next] | [standalone]

#72088

On 2025-08-23 14:22, Stéphane CARPENTIER wrote:
> Le 19-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit :
>> On 2025-08-16 20:28, Rich wrote:
>>> Stéphane CARPENTIER <sc@fiat-linux.fr> wrote:
>>>> I never use "diff". I really don't like the way it's displayed. I'm using
>>>> "vimdiff" or "nvim -d" a lot, because at the same time it's easier to
>>>> see what I want and it's easier to make the right changes.
>>>
>>> diff's default output is an 'ed script' which is not very human
>>> readable at all.
>>>
>>> The unified output (-u option) provides a 'diff' view that is much more
>>> ameniable to being understood by humans.
>>>
>>
>> diff --side-by-side --suppress-common-lines --ignore-space-change \
>>      $1 $2 | less -S
> 
> I'm still not convinced. OK, it's a little bit better to read than the
> default. But it's still very poor compared with vimdiff/nvim -d. And,
> unlike vim/neovim, it's still useless to report some change in a file to
> another file.
> 
>> But lately what I use is "meld".
> 
> OK, I looked at it a little bit, it's the same information level than
> vimdiff/nvim -v. But it looks more mouse driven than keyboard driven and
> I'd have to learn something new.
> 

In my notes I have:

utils diff
         kdiff3
         tkdiff *
         fldiff
         meld - very good comparison editor



-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#72147

Le 23-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit :
> On 2025-08-23 14:22, Stéphane CARPENTIER wrote:
>> Le 19-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit :
>> 
>>> But lately what I use is "meld".
>> 
>> OK, I looked at it a little bit, it's the same information level than
>> vimdiff/nvim -v. But it looks more mouse driven than keyboard driven and
>> I'd have to learn something new.
>> 
>
> In my notes I have:
>
> utils diff
>          kdiff3
>          tkdiff *
>          fldiff
>          meld - very good comparison editor

Like I said unlike diff, it looks OK to have easily the most important
informations about the changes. So, yes, it looks good. Now, I'm a
vimist, so if it doesn't bring me more than vim, I don't see the point
on using it. Never heard about it, never heard about the others neither.

-- 
Si vous avez du temps à perdre :
https://scarpet42.gitlab.io

[toc] | [prev] | [next] | [standalone]

#72185

On 2025-08-24 13:15, Stéphane CARPENTIER wrote:
> Le 23-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit :
>> On 2025-08-23 14:22, Stéphane CARPENTIER wrote:
>>> Le 19-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit :
>>>
>>>> But lately what I use is "meld".
>>>
>>> OK, I looked at it a little bit, it's the same information level than
>>> vimdiff/nvim -v. But it looks more mouse driven than keyboard driven and
>>> I'd have to learn something new.
>>>
>>
>> In my notes I have:
>>
>> utils diff
>>           kdiff3
>>           tkdiff *
>>           fldiff
>>           meld - very good comparison editor
> 
> Like I said unlike diff, it looks OK to have easily the most important
> informations about the changes. So, yes, it looks good. Now, I'm a
> vimist, so if it doesn't bring me more than vim, I don't see the point
> on using it. Never heard about it, never heard about the others neither.

Sure, I'm just mentioning the existence of other tools, should other 
people read this.

tkdiff is, I think, another editor tuned to file comparison. I don't 
have installed kdiff3 nor fldiff, so I can't comment.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#72204

On 24 Aug 2025 11:15:36 GMT, Stéphane CARPENTIER wrote:

> Now, I'm a vimist, so if it doesn't bring me more than vim, I don't see
> the point on using it.

I wrote custom commands for Emacs that let you do diffs on selected 
*parts* of files.

<https://gitlab.com/ldo/emacs-prefs/-/blob/master/diffbuff.el>

[toc] | [prev] | [next] | [standalone]

#71821

Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:

> How about a list of favourite options to common commands?
> Mine is "ls -ltr", which shows files in chronological order.

For ls, I have

- lsl is aliased to ls -lLF. I sometimes remove the L and then put it
  back because sometimes I want to see symlinks as symlinks and
  sometimes I don't. I think I'm tending towards seeing the symlinks
  again. 
- l is aliased to ls -lF|more or more -e now to retain the old behavior,
  i.e. paging only paging needed, exit otherwise.
- lth is a function to run ls -lt | head -20 on its arguments or $PWD if
  no arguments.
- I'm thinking of replacing the l alias with a function so it can be run
  on multiple directories and retain color. Something like
  ls --color=always -lF $* | less -iX -E -R

[toc] | [prev] | [next] | [standalone]

#70945 — Re: I?m A Linux Expert, And Here Are 6 Commands I Can?t Live Without

Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
> <https://www.zdnet.com/article/im-a-linux-expert-and-here-are-6-commands-i-cant-live-without/>
> 
> What?s an obvious omission from his list? To me, it?s the ?find?
> command. I have millions of files on my main machine (quite literally,
<snip>

zdnet, or I like windows magazine, what does one expect :)

Yes, if someone does not know how to use find(1), they are
no expert to me. 

> With the command chmod u+x filename....

On some file systems doing that will not give you the
ability to execute the script.  I think he could have
come up with a much better example. :)


-- 
[t]csh(1) - "An elegant shell, for a more... civilized age."
                        - Paraphrasing Star Wars

[toc] | [prev] | [next] | [standalone]

#71055

Lawrence D'Oliveiro <ldo@nz.invalid> writes:

> <https://www.zdnet.com/article/im-a-linux-expert-and-here-are-6-commands-i-cant-live-without/>
>
> What’s an obvious omission from his list? To me, it’s the “find”
> command.

Possibly or something like it. I just started looking into rawhide which
is another search tool. My interest is rawhide's ability to search for
tags in extended attributes. I've started adding tags to videos and
photos so I can search for those with rawhide.

[toc] | [prev] | [next] | [standalone]

Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →

Back to top | Article view | comp.os.linux.misc

csiph-web