Multiple segments with the same fetching information property

[accedo-robcc]

If I were to have multiple segments with the same fetching information (eg. fetch_status), is that less performant than having both on the same segment?

{
  "type": "git",
  "style": "plain",
  "foreground": "p:blue",
  "properties": {
    "fetch_status": true
  },
  "template": "{{ if gt .Ahead 0 }} \u2191{{.Ahead}}{{end}}{{ if gt .Behind 0 }} \u2193{{.Behind}}{{end}} "
},
{
  "type": "git",
  "style": "plain",
  "foreground": "p:blue",
  "properties": {
    "fetch_status": true
  },
  "template": "{{ if gt .Working.Added 0 }}+{{ .Working.Added }} {{ end }}{{ if gt .Working.Modified 0 }}<p:git-modified>~{{ .Working.Modified }}</> {{ end }}{{ if gt .Working.Deleted 0 }}-{{ .Working.Deleted }} {{ end }}{{ if gt .Working.Untracked 0 }}?{{ .Working.Untracked }}{{ end }} "
}

[lewis-yeung]

The performance impact of a git segment is usually more significant when we're in a large-sized local repo.

[accedo-robcc]

but if I separate a git segment into two (with the same fetch flag), am I duplicating the performance needed? Or is the git status "cached" instead of being fetched twice

[JanDeDobbeleer]

@accedo-robcc it's fetched twice. Unless if you use cross segment properties in a text segment for example.

[accedo-robcc]

good to know, and thanks for the link!